Domain: hungry.com
Stories and comments across the archive that link to hungry.com.
Comments · 38
-
Re:I'd call that "fried"
Bricks can be fixed with JTAG; if you have to outright replace the hardware, that's fried, toasted, nuked. (How the HELL does software do something THAT bad, anyway? Even flashing a ROM for an entirely incorrect model on a smartphone is still technically reparable..)
http://www.hungry.com/~jamie/hacktest.text
0133 Ever fix a hardware problem in software?
0134 ... Vice versa?...
0141 Ever physically destroy equipment from software?
-
Ask Petter Reinholdtsen (DebianEdu/Skolelinux)
Petter Reinholdtsen of Debian Edu/Skolelinux fame will have a lot of useful no-nonsense suggestions. Contact information at http://www.hungry.com/~pere/ .
-
Java is already fragmented
Java is already fragmented. The result of open sourcing Java will actually be consolidation, i.e. killing of competing VMs. And a huge open source test suite will greatly benefit all surviving JVMs, which is a good thing.
How can you not see this?
Javas problem is not that it might get fragmented, the problem is that it IS fragmented. Do something about it! Let Java free! -
Re:weekend?Why couldn't they wait till the weekend, or at least after hours, instead of disrupting children's school day?
The obvious answer is that the employees of the school will be there during school hours... making the search a lot easier.
Just to throw this out there.. from this story, we know the warrant has two options for when the search will take place:
1) In the Daytime, from 6am-10pm
2) At any time day or night as I find reasonable cause has been established.The judge would not permit the nighttime search. To make sure you have enough time, you would want to start the search early in the day. And for a copyright infringement case, why make the FBI work weekends? During the school day is the obvious choice - but you could schedule it for a day the students were gone, maybe wait until summer.
-
Yet Another Amusingly-Named X Replacement
So why is it going to succeed where these failed?
:
fresco
YAX (Y Ain't X)
The Y Window System
Oh never mind. What's the point? -
FYI...
FYI, Chris Toshok (toshok), the person who wrote up this experience is also one of the head programmers on Ximian's Evolution mail client.
-
Hungry Programmer's Y.
It's an obvious name for an X successor, of course, but there is (well, was) a Y Windowing System in development by the Hungry Progammers
-
Re:Bad choice of name
and the Y in the hungry programmers window system is actually a cyrillic character and it's pronounced completely different.
-
Bad choice of name
Unfortunately, the name Y Window System has already been taken by the Hungry Programmers. Still, Z is probably free
:-P. -
Name collisions
People should know that there has been at least one project called "Y Window System" already (Not to mention W and Z...):
Here, 1998 vintage
There was also the YY window system. but that's long dead - 1992 era.
-
Re:Dynamic HTML
I agree 100%.
go here if you have javascript enabled. This guy is not very fond of javascript! -
Re:Ex-Squeeze-Me?!
Followup:
This page opens up a BBC java nav bar, which, according to the java security model, should not be able to. I tested this with MSIE for Mac, and the bar was not loaded. Mozilla Firebird for OSX also loads the applet (im)properly -
Re:How about XWindows?
When can we expect Y Windows to be released?
Not for a while. The web site has not been updated since 1998.
-
Fairly simple!?Your implication that Cocoa can't handle a complex GUI is ridiculous. Sputter, fume...words fail me.
rjrjr
-
Fairly simple!?Your implication that Cocoa can't handle a complex GUI is ridiculous. Sputter, fume...words fail me.
rjrjr
-
Fairly simple!?Your implication that Cocoa can't handle a complex GUI is ridiculous. Sputter, fume...words fail me.
rjrjr
-
Fairly simple!?Your implication that Cocoa can't handle a complex GUI is ridiculous. Sputter, fume...words fail me.
rjrjr
-
Re:Gnu ROPE questionThe most recent reference to it that I could find was April 2001 on netscape.public.mozilla.performance, where shaver is quoted:
everything I have is at http://www.hungry.com/~shaver/gropt.tar.bz2 but it's not for the faint of heart, and I don't have time to talk people through it.
Back in late 1998 lwn ran a status report of GNU Rope by Nat:
What is the status?
The link-time optimizer is fully working, benchmarks indicate 30% less memory usage, and it is better than twice as fast on many machines.
The ordering algorithms need tuning. The post-link optimizer needs debugging. It will be released soon:
-
Re:Gnu ROPE question
This question made me quite curious as well. A google search just results in lots of postings asking "Where'd it go?"
There's also a paper and some slides. So, I'll reiterate the question... where'd it go? -
Re:Gnu ROPE question
This question made me quite curious as well. A google search just results in lots of postings asking "Where'd it go?"
There's also a paper and some slides. So, I'll reiterate the question... where'd it go? -
DONT
No, please, not another windowing system. X11 is fine for most purposes and, if you need something is does not provide, write an extension. There are more than enough 'alternatives' that are either designed for niches, have never been finished or will never get a significant marekt share. They don't have any significant advantage, at least as a general window system, and they lack applications. And despite those people who claim that X11 is sooo bloated (usually because they see the memory usage and do not realize that most of the memory is taken by pixmaps that won't take less space in other solutions) there are proofs like TinyX and WeirdX.
-
Re:Fonts: main Linux hindrance
-
Re:X Windsows
There is actually already a windowing system called Y windows.
X isn't going to be replaced anytime soon. It doesn't really need to be either... Xprotocol was designed to be added to and updated, it's just that people haven't had the motivation to do it until recently.
-
There already is
Behold: the Y Window System. Check out the overview. It shows promise, but then, we've been saying that about Berlin for years now.
-
There already is
Behold: the Y Window System. Check out the overview. It shows promise, but then, we've been saying that about Berlin for years now.
-
The Y Window system already exists
Check it out.
-
Re:Wait a stinking minute.....
No, I'm pretty certain that Y was a replacement for X (Window, that is). Hang on a minute... ah, found it. Take a look here.
-
Re:If its gonna replace X..
Check on the Hungry Programmers' site. They're the guys who developed it (or started developing it - I have no idea what stage it's at, if it's finished/unfinished, etc.)...
-
LessTif Needs More than "Finishing Work"
I agree with almost everything Richard Stallman has to say on this one. The only major beef I have with Stallman's open letter is with the following sentences: "Most programs that were written for Motif can use LessTif with no changes. Please support the free software community by using LessTif rather than Motif. Some finishing work still needs to be done on LessTif; to volunteer, contact lesstif@hungry.com."
Stallman's use of the term "finishing work" is misleading. Stallman fails to point out that LessTif presently implements the base, CDE-unaware Motif 1.2 widget library and little else. mwm, UIL, and libMrm are a long way from merely requiring "finishing work." The Hungry Programmers plan to support Motif 2.1 but freely admit in the LessTif FAQ that compatibility with Motif 2.0 will "take a long time."
Beyond having "made room for CDE compatible widgets and applications," the prospects for CDE implementation are murkier. The LessTif FAQ says that "the people in the eXode project...are working on" CDE, but the Enhanced X Open Desktop (eXode) Project Goals page flatly states that "eXode won't be the free CDE."
Thus, it's a stretch to say that the current LessTif requires only "finishing work" to be fully compatible with Motif 1.2, and it's even more questionable if the aim is parity with OpenMotif 2.1.30, let alone CDE.
By the way, the above is not meant to put down the LessTif project or the A HREF="http://www.hungry.com/">Hungry Programmers -- they've done excellent work thus far.
If everyone were to switch to LessTif in its current form, there'd be little, if any, incentive for anyone to move forward from Motif 1.2 to Motif 2.1 -- Motif would either ossify or fork at 1.2, and either way, Motif 2.1 (even as an API) would more or less cease to exist. Those who wrote their programs to the Motif 2.1 API would have to back-port their code to work with the Motif 1.2-based LessTif API (or switch GUI toolkits altogether). I won't offer my position on that issue at the moment, but when advocating LessTif as an alternative to OpenMotif, Stallman should have at least acknowledged it.
Stallman may or may not merely be assuming that any release of Motif beyond 1.2 is irrelevant (since, like it or not, Motif 1.2 is still the predominant version in use), but it is careless of him, and a little troubling, that he doesn't mention it at all.
However, this quibble aside, I agree with the thrust of what Stallman wrote.
-
Re:(OT) Rant on rants, maybe flamebait
I have had it up the socket with people complaining about nearly every story on
/., saying that it "doesn't belong" or isn't "news for nerds" or it isn't "stuff that matters". Last I checked, no one had defined those in a universally acceptable way.
Some things don't matter to some people. Some things do. Sometimes I care about a /. posting. Sometimes I don't. If I don't find it interesting, I can skip it, and I can even configure my account to filter out stuff I'm not interested in. WE'RE ALL DIFFERENT (tm) HERE. Why do some feel the need to decrease the s/n ratio by complaining about stories they don't feel are relevant to *their* beliefs on what's important? Imagine if the same thing happened everytime someone spammed a usenet group... <ugh>
When I saw the review pop up, I questioned (to myself) its relevance. Yes, it is only marginal. And I dug a little deeper about why I was questioning it at all. I certainly skip enough articles that don't interest me which are clearly within the charter of Slashdot. The bottom line is that I am feeling lousy today. I'm hungry for any interesting news and I'm hoping that the next Slashdot story will be it. I wasn't disappointed because it was a movie review, or because it was by Jon Katz. I rarely agreee with him completely, but his articles generate some good discussions here. I was disappointed because I want some Nerd News. Well it isn't Slashdot's fault and it isn't Jon's fault that this story came up first.
There is a fine line that the guys at Slashdot are walking. It would be easy enough to expand Slashdot to report every open source software announcement, every new SF movie, every cool piece of new hardware, etc. Instead of a manageable number of stories that everyone can scan any time they're here, we would start to get people missing stories, people filtering heavily and so forth. Slashdot would die from lack of any definition. The community here, contentious as it is, would fragment.
I have a copy of the Hacker Test sitting in my briefcase. Among the many questions, it asks:
- 0490 Do you read news?
- 0491
... More than 32 newsgroups? - 0492
... More than 256 newsgroups? - 0493
... All the newsgroups?
When was the last time you considered reading all of Usenet? It is huge, largely unmoderated, and ill-defined. I still enjoy some newsgroups occasionally, but it has lost most of the feeling that a newsgroup was a community with some common interests. Achieving that requires some boundaries. There are some things that are simply off-topic. But is requires some acceptance of diversity in the group. And it requires a small enough body of shared information that we are all exposed to a significant portion of it. We are creating, on an ongoing basis, a community here. We are creating the shared experience.
Questioning the boundaries of the group comes with the territory. If this article was ovr the boundaries, by consensus, or by reflection after the fact by the Slashdot Gods, so be it. They can step back from the edge. If this is part of what Slashdot is and will be, I can accept that it is not so far from the other interests that draw me here that it will undermine the benefits I get from what I read here.
-
Re:Three I would have added...One of The Hungry Programmers (of Lesstif fame) claimed that cutesy name a while back. He can have it. BTW, Berlin was a play on the words MS used to describe its upcoming versions of Windows (Cairo, Chicago, Daytona, etc.) at the time. Everyone's suggested renaming it but can't agree on what to change it to.
Anyway, if you've clicked through, you've noticed that Hungry's Y makes the Freedows project look productive. It's somewhere between "I've got some ideas, a few names, and a cool web page" and "I might be getting around to coding this." It appears that the author may have found smaller windmills to tilt at.
-
Re:Long Live Y ?
http://terror.hungry.com/products/Ywind ows/
Not much there yet, it seems.
-
X AlternativesI agree that X is a little cruddy. It is too thoroughly networked, so there's a fair amount of overhead in performing local operations. It also takes up a lot of RAM. Oh, and it has too much heritage behind it; it really was meant for black and white display, and color hacks atop it make code that supports multiple display depths a massive mess. Luckily toolkits can get rid of most of this pain, but still, if these toolkits could be ported to a new X, that would be neat.
There are two X alternatives that I can think of besides the Berlin mentioned. One of them is The Y Window System, by the Hungry Programmers (specifically Christoph Toshok), which isn't very far along and as far as I can tell hasn't been worked on in a while (since about February 1998). It promotes the use of a single fixed depth, which I think is a bad idea. It does have some good ideas though, like a somewhat separate memory architecture. Download here.
The other one, NanoGUI, was originally developed by Alan Cox. It was designed with a lightweight memory footprint in mind. I'm not sure if it supports networked display, though, but I believe they're going to at least port VNC. It's being used on the new Linux7k project, which is attempting to create a usable Linux system for the Psion 5 series palmtop (it uses an ARM7 processor). It seems to be undergoing active development. Download here.
So I hope that's a good starting point.
-
X AlternativesI agree that X is a little cruddy. It is too thoroughly networked, so there's a fair amount of overhead in performing local operations. It also takes up a lot of RAM. Oh, and it has too much heritage behind it; it really was meant for black and white display, and color hacks atop it make code that supports multiple display depths a massive mess. Luckily toolkits can get rid of most of this pain, but still, if these toolkits could be ported to a new X, that would be neat.
There are two X alternatives that I can think of besides the Berlin mentioned. One of them is The Y Window System, by the Hungry Programmers (specifically Christoph Toshok), which isn't very far along and as far as I can tell hasn't been worked on in a while (since about February 1998). It promotes the use of a single fixed depth, which I think is a bad idea. It does have some good ideas though, like a somewhat separate memory architecture. Download here.
The other one, NanoGUI, was originally developed by Alan Cox. It was designed with a lightweight memory footprint in mind. I'm not sure if it supports networked display, though, but I believe they're going to at least port VNC. It's being used on the new Linux7k project, which is attempting to create a usable Linux system for the Psion 5 series palmtop (it uses an ARM7 processor). It seems to be undergoing active development. Download here.
So I hope that's a good starting point.
-
Re:Y?
Nope.
Berlin is at http://www.berlin-consortium.org
Y windows is at http://www.hungry.com/products/Ywindows
YAX is at http://yax.netpaedia.net
-
Re:Y?
-
Re:Y?
-
GNOME doesn't depend on X, and shouldn't
Berlin isn't likely to be lightweight since they have included a widget system in the display server.
Maybe Chris Toshok's Y Window System will happen, but X compatibility (via a libX11 proxy lib or proxy X server) will be required forever.