Re:Incidental success...
on
Bitter EJB
·
· Score: 1
Why the hell didn't somebody try using this hunk-a-junk before they released their 1.0 spec, or maybe their 1.1 spec, or howzabout the 2.0 spec?
You could ask that about a lot of Java APIs. I mean, they can't even get the basic collection classes right.
Re:EJB is REALLY Bitter
on
Bitter EJB
·
· Score: 3, Insightful
One, for those who wish to develop components for use within the EJB framework, there is a small set of interfaces and objects.
And a completely different set of deployment descriptors for every single EJB container, meaning you can't take your EAR file developed for (say) JBoss and deploy it on WebSphere or BEA. That, to me, is one of the biggest problems with EJB--zero portability of the finished packaged code. Wasn't Java supposed to be 'write once run anywhere'?
Hmm, well, I don't read any read-only web journals. What's the point? If I want read-only opinions I'll read a newspaper or magazine. I'd rather use the web for something better.
I'd rather live my life with a chance of being blown up by a terrorist rather then live in a police state.
Of course, that's implicitly assuming that the opposition's claims are true. In reality, how many police states can you think of where you'd be safer than you are in a liberal democracy? If police states lead to safety, people would flock to them, as we already know most people value safety over freedom.
I also mention that, in a truly bizarre finding, the Israeli ID card experience 90% mimics that of the Nazi Germany ID card experience (right down to the letter "J" indicating if the person is Jewish or not.)
Well, not very bizarre really. It's just like the Pilgrims who sailed to America--they didn't really want a new land where nobody would be oppressed for their religious beliefs; they just wanted a place where they would be the ones doing the oppressing.
Radiation from the eruptions travels at the speed of light, right? So how do we find out about them hours before they start? Is there some method for telling when an eruption is going to happen soon?
I didn't say Microsoft didn't document anything. I was merely demolishing the argument that Apple's systems are closed and proprietary and undocumented.
Sure, they haven't released source code for everything. But that's not the same as the system being closed. Apple generally does an excellent job of documenting their systems and making them easily extensible. You don't even need to sign an NDA or register to get the documentation.
Right. Syncing's always gonna be slow via SMB, unless you have gigabit ethernet in your house, which I suspect isn't the case--because your network connection will never get close to the 25MB/s or more that can be transferred via Firewire.
Actually, I fixed a problem in Gentoo where there was an "argument list too long" caused by use of xargs. I removed the xargs and made find call rm directly.
If you read the text you just linked to, it clearly states that yes, you still need to install the daemontools stuff even if you don't use it to start the daemon.
I would have installed djbdns if it wasn't for that.
In the end, I only needed a local caching forwarding DNS server, so I went with dnsmasq instead.
It needs about 2x the pocket space of a Game Boy Advance SP.
It has a tiny screen, about 2/3 the size of a Palm device, half the size of a GBA-SP.
It's complicated. I fiddled around with one for a while trying to work out how to make a game start, then gave up.
It's bigger than any other phone on the market, and you'll look a complete tool if you try to use it as one, so good luck selling it at phone stores.
You have to take it apart and hold a bunch of small, easily lost parts and screws in your hand while you remove the battery, just to change game cartridge.
It's $300, meaning you could get a GBA-SP, a tiny mobile phone with organizer built in, and still have just enough money for a refurb iPod, instead of buying this monumentally ill-concieved toy.
The mystery to me is how Nokia ever allowed the thing to get to market.
In fact, one of the big strengths of C# is that, unlike Java, C# makes it easy to reuse existing C and C++ libraries...
BFD. I can write in Objective-C for Cocoa on OS X or GNUStep on Linux and have all those advantages--plus native code and proper polymorphism. In addition, Objective-C is trivial to learn if you know C--unlike C# or C++.
Slashdot Mirror
You could ask that about a lot of Java APIs. I mean, they can't even get the basic collection classes right.
And a completely different set of deployment descriptors for every single EJB container, meaning you can't take your EAR file developed for (say) JBoss and deploy it on WebSphere or BEA. That, to me, is one of the biggest problems with EJB--zero portability of the finished packaged code. Wasn't Java supposed to be 'write once run anywhere'?
Hmm, well, I don't read any read-only web journals. What's the point? If I want read-only opinions I'll read a newspaper or magazine. I'd rather use the web for something better.
Of course, that's implicitly assuming that the opposition's claims are true. In reality, how many police states can you think of where you'd be safer than you are in a liberal democracy? If police states lead to safety, people would flock to them, as we already know most people value safety over freedom.
Well, not very bizarre really. It's just like the Pilgrims who sailed to America--they didn't really want a new land where nobody would be oppressed for their religious beliefs; they just wanted a place where they would be the ones doing the oppressing.
Suicide is only harmless to society if the victim is truly friendless, unloved and nothing but a burden to others.
The problem is, most suicides *aren't* worthless friendless unlovable human beings. They're just ill.
See also: "Bowling for Columbine".
Radiation from the eruptions travels at the speed of light, right? So how do we find out about them hours before they start? Is there some method for telling when an eruption is going to happen soon?
So, if Apple's going to make me mess around to get a shell I don't actively loathe, I may as well consider all the possibilities.
So... which shell should I use, and why?
To give you some ideas for what I'm looking for:
- I don't care about scripting. If I want to write a script, I'll use a scripting language.
- Mnemonic commands are good.
- Good command-line editing that uses sensible keystrokes (e.g. Home and End work) is good.
- Small memory requirements and high CPU efficiency are very good.
1. You have too much disk space, and want a shell that's 50% bigger.
2. Setting environment variables via setenv is too intuitive, you'd prefer a stupid non-mnemonic command like "export" (to what?)
3. You'd rather run scripts in a huge shell than in a compact scripting language suited to the task such as python or perl.
4. You have a bizarre belief that your scripting language and your interactive shell need to be the same program.
5. You worship Richard Stallman.
...which probably isn't the default because it's freakin' slow.
Mail.app in 10.2 checks all IMAP folders for me. Maybe your IMAP server is broken?
Read the posting I was replying to. You know, the one I quoted, dumbass.
I didn't say Microsoft didn't document anything. I was merely demolishing the argument that Apple's systems are closed and proprietary and undocumented.
Sure, but what if they don't want to be used for medical experiments and farmed for spare organs for the rich?
Let's see... How about the open paper describing the complete QuickTime file format? Or the documentation for creating your own codecs and components? Or the documentation for the Quartz Window Manager, including how to send it raw PDF and details of the level of PDF supported by current versions? Or the documentation for how to hook into the window manager and remote control it?
Sure, they haven't released source code for everything. But that's not the same as the system being closed. Apple generally does an excellent job of documenting their systems and making them easily extensible. You don't even need to sign an NDA or register to get the documentation.
Maybe you're right. Point is, xargs isn't a panacea. It can cause problems as well as solving them.
Same here, however the performance is crappy compared to using other protocols like daap and http.
Right. Syncing's always gonna be slow via SMB, unless you have gigabit ethernet in your house, which I suspect isn't the case--because your network connection will never get close to the 25MB/s or more that can be transferred via Firewire.
Actually, I fixed a problem in Gentoo where there was an "argument list too long" caused by use of xargs. I removed the xargs and made find call rm directly.
For playback, use daapd or stream the MP3s via Apache. Windows' SMB performance sucks.
If you read the text you just linked to, it clearly states that yes, you still need to install the daemontools stuff even if you don't use it to start the daemon.
I would have installed djbdns if it wasn't for that.
In the end, I only needed a local caching forwarding DNS server, so I went with dnsmasq instead.
It's the size of an original Game Boy Advance.
It needs about 2x the pocket space of a Game Boy Advance SP.
It has a tiny screen, about 2/3 the size of a Palm device, half the size of a GBA-SP.
It's complicated. I fiddled around with one for a while trying to work out how to make a game start, then gave up.
It's bigger than any other phone on the market, and you'll look a complete tool if you try to use it as one, so good luck selling it at phone stores.
You have to take it apart and hold a bunch of small, easily lost parts and screws in your hand while you remove the battery, just to change game cartridge.
It's $300, meaning you could get a GBA-SP, a tiny mobile phone with organizer built in, and still have just enough money for a refurb iPod, instead of buying this monumentally ill-concieved toy.
The mystery to me is how Nokia ever allowed the thing to get to market.
Uh, what you describe sounds exactly like IBM policy to me, last time I certified that I had read it.
BFD. I can write in Objective-C for Cocoa on OS X or GNUStep on Linux and have all those advantages--plus native code and proper polymorphism. In addition, Objective-C is trivial to learn if you know C--unlike C# or C++.