I'm fine with my own code being under GPL, the problem with CPL is that the CPL requires that extra clauses be added to the conditions of use, which GPL expressly permits. So it's impossible to legally mix GPL and CPL libraries, even if you want to release your own code as GPL.
Hopefully this new version fixes the problem. If it does, this is the first step towards getting an implementation of SWT on top of Qt (the next step is obviously, convincing Trolltech to "upgrade" to the new license.)
People should also scold Microsoft for using the name "Avalon", which will only cause confusion since both Avalons are architectures for developing applications.
While he focuses on Windows, Spolsky is not a fanatic believer in one approach over another; if C# works better than Visual Basic for a specific task...
Well yeah, if both options are evil, of course you can't get fanatical about one approach over the other. Sheesh.
Not really. It was numbered as a sequel, but in spirit it was really a remake. You can happily remove I from any trilogy and get a working "trilogy in two parts."
Surely the templates and the template assembly application are two different things. Can't they just fix the templates? If they can't, then Slashcode itself just sucks, and they should move to something more capable.
I would prefer CSS through w3m and Links. Please DO FIX SLASHCODE. It would give more space back to the article and get rid of the enormous space taken up by the sidebar.
Duh. It was still a bloody good description of how to do it. Any excuses like the above would only come from a Slashdot maintainer who didn't want to put in the effort.
Who would pay $30 for something which sucks?
on
Firefox News Roundup
·
· Score: 1
Not everyone likes Opera. Fast? It ran slower than Konqueror on my machine. And the worst thing is, Opera is based on Qt, but still can't manage to look integrated with KDE. That's just pathetic IMO.
I bet part of it is that it's using tables extensively for its layout, instead of easier ways (easier for the browser, that is) like DIV+CSS.
If the right bar was "right: 16px; width: 150px" then we would know exactly where it goes. But since it's in a table, we might as well just let it be random until Slashdot fix it.
Haven't JavaCards been usable for this sort of thing since... well, forever?
This is just another ".NET tries to catch up to Java" article. Move along...
And even before then, I remember magnetic strip cards being usable for authentication. Heck, I helped hack a crappy magnetic-based system together for one of my previous jobs!
I think the difference here is that this exploit is likely to be fixed within a six month time span.
I'm fine with my own code being under GPL, the problem with CPL is that the CPL requires that extra clauses be added to the conditions of use, which GPL expressly permits. So it's impossible to legally mix GPL and CPL libraries, even if you want to release your own code as GPL.
Hopefully this new version fixes the problem. If it does, this is the first step towards getting an implementation of SWT on top of Qt (the next step is obviously, convincing Trolltech to "upgrade" to the new license.)
Yes, Sun is heavily threatened by an OS they're using on their very own Java Desktop System. In other news, Microsoft is threatened by Windows!
I suppose it could run BSD... if BSD weren't dead! There you go, I fused another one into the mix.
My VIA motherboard also worked out of the box, and I didn't have to install any extra, closed source drivers, either.
Yeah, that's a much better example.
People should also scold Microsoft for using the name "Avalon", which will only cause confusion since both Avalons are architectures for developing applications.
Damnit, they should have namespaced it!
What I liked was this one:
While he focuses on Windows, Spolsky is not a fanatic believer in one approach over another; if C# works better than Visual Basic for a specific task...
Well yeah, if both options are evil, of course you can't get fanatical about one approach over the other. Sheesh.
Not really. It was numbered as a sequel, but in spirit it was really a remake. You can happily remove I from any trilogy and get a working "trilogy in two parts."
If they're being protected, they're not much of a hunter.
Toaster? A second ago, we were talking about GameBoys.
Surely the templates and the template assembly application are two different things. Can't they just fix the templates? If they can't, then Slashcode itself just sucks, and they should move to something more capable.
And besides not getting used, I haven't heard of problems with windows update.
Let's see...
That's just the three problems which come to mind. I'm certain that there are more.
/me hands Slashdot a lesson on Permalinks
I would prefer CSS through w3m and Links. Please DO FIX SLASHCODE. It would give more space back to the article and get rid of the enormous space taken up by the sidebar.
It will be a very small array. The number of browsers which actually work well is less than the number of browsers released under the name "Firefox".
1. I knew all three of the above. :-)
2. None of them actually answered my question.
3. Congratulations on the most useless response today.
Duh. It was still a bloody good description of how to do it. Any excuses like the above would only come from a Slashdot maintainer who didn't want to put in the effort.
Why not complain to the people who caused it.
Not everyone likes Opera. Fast? It ran slower than Konqueror on my machine. And the worst thing is, Opera is based on Qt, but still can't manage to look integrated with KDE. That's just pathetic IMO.
Yeah, but how long until it's in stable?
I bet part of it is that it's using tables extensively for its layout, instead of easier ways (easier for the browser, that is) like DIV+CSS.
If the right bar was "right: 16px; width: 150px" then we would know exactly where it goes. But since it's in a table, we might as well just let it be random until Slashdot fix it.
The stupid thing is that somebody already did all the work for them but they STILL don't fix it.
Slashdot's developers suck.
Easy enough. Let's just define the "Natural Language" is Lojban. Computers can parse that unambiguously...
Haven't JavaCards been usable for this sort of thing since... well, forever?
This is just another ".NET tries to catch up to Java" article. Move along...
And even before then, I remember magnetic strip cards being usable for authentication. Heck, I helped hack a crappy magnetic-based system together for one of my previous jobs!
An installer? WTF? I'll have to change distros if it gets too easy!
A cop-out. They caused the delay in the first place, therefore it's their fault.