I think I know the first thing I'm going to do when the source gets released -- fix all those bizzare GUI widgets.
The "click on this side of the button to increase the value, click on the other side to decrease, and drag to change smoothly" (all on a standard-looking button) is really dumb.
I'm not sure the method for using it should change that much, but it could at least seriously use some visual affordances.
Well, some expenses (like running the website) are ongoing, though. That buffer'll keep 'em for a bit, but we probably should drop some change into the till now and then to keep them going.
What happens the first time someone registers billyg@microsoft.com?
microsoft.com's jabber server (as designated by the relevent DNS SVC records) would have to allow them to do that.
Registration @ a particular domain is controlled by the jabber server(s) for that domain. Like email.
Most Jabber servers right now allow open registration, but there's no requirement that they do. And anyway, I don't think microsoft.com is operating a jabber server yet.
Actually, such a facility exists in Windows. The MSHTML stuff is just one possible implementation. There's actually a project that bundles mozembed to provide an implementation of the same interfaces.
(incomplete, though, but only because they aren't adequately documented)
For example, my old car topped out at 50 mph. My new car's max is 100 mph. It is 100% faster. My old car went 50 miles in 1 hour. My new car goes 50 miles in 30 minutes. The time it takes to travel anywhere has been reduced by 50%. If it were reduced by 100%, though, I'd be violated several laws of physics, I think.
Well, it sounds like you'd be in violation of several state laws, at least. ^_-
Or perhaps the other way around...
on
.NET for Apache
·
· Score: 2
What you say is true about the messiness and incompleteness (and redundancy!) of many aspects of Common Lisp.
With the benefit of hindsight, Common Lisp needs a LOT of cleanup. But as far as its feature set, all modern languages are converging on it (and have yet to get there), not the other way around.
Java and C#/CLR should receive a thorough overhaul, incorporating some of the really nifty dynamic features that Common Lisp provides (and has provided since the ancient times of computing).
(continuations, for example... or macros [ macros in the Lisp sense, which is a totally different thing than what most languages mean by macros]... or CLOS's multiple dispatch)
Actually I've been following Wine for a while, and it seems like the biggest thing holding them back was that (until recently) they didn't do any regression testing.
They'd fix one thing only to break like five or ten others.
Interestingly, now that they're moving forward with an exhaustive testing regime, they've started filling in the remaining pieces pretty fast.
And, indeed, most Open Source projects don't do much in the way of testing...
Ah, I wasn't thinking of C++ development, but thank you. It's a good link.
What I said is easily true of C development, but anyone concerned with C++ should definitely read that FAQ entry as the libg++ licensing situation is a little more complex (though not too bad; it's just important to know what to link with).
The way this should have been done is to coerce the HTML into w3c-valid HTML4, and then only pass whitelisted tags, attributes, and URL schemes.
It might distort non-well-formed HTML, but if the HTML isn't well-formed to begin with all bets are off anyway.
I realize that would require quite a few more server resources to implement. Too bad. As it is this ill-thought-out scheme appears to stand a real chance of permanently distorting the English language.
One does wonder if the Chinese government (or any government, really... but they're the ones Yahoo!'s been making deals with lately) will see the potential here for interfering with dissident speech.
Yeah, like the ones who developed algebra [hint: al-gebra is an arabic word], or preserved and translated many of the surviving writings of the ancient world.
I think I know the first thing I'm going to do when the source gets released -- fix all those bizzare GUI widgets.
The "click on this side of the button to increase the value, click on the other side to decrease, and drag to change smoothly" (all on a standard-looking button) is really dumb.
I'm not sure the method for using it should change that much, but it could at least seriously use some visual affordances.
Well, some expenses (like running the website) are ongoing, though. That buffer'll keep 'em for a bit, but we probably should drop some change into the till now and then to keep them going.
microsoft.com's jabber server (as designated by the relevent DNS SVC records) would have to allow them to do that.
Registration @ a particular domain is controlled by the jabber server(s) for that domain. Like email.
Most Jabber servers right now allow open registration, but there's no requirement that they do. And anyway, I don't think microsoft.com is operating a jabber server yet.
Actually, such a facility exists in Windows. The MSHTML stuff is just one possible implementation. There's actually a project that bundles mozembed to provide an implementation of the same interfaces.
(incomplete, though, but only because they aren't adequately documented)
Well, it sounds like you'd be in violation of several state laws, at least. ^_-
In the case of Earth and the sun, I have no idea of the timescales involved.
. ht m
http://www.owlnet.rice.edu/~raskka/tidallocking
Hit google for "tital locking" and "spin-orbit locking", and you'll probably find a lot more.
Actually the Earth is very slowly settling into being tidally locked with the Sun, much like the moon is tidally locked with earth.
Eventually, one side of the Earth will end up facing the Sun constantly. However, it'll take a very long time.
It would certainly end people there.
If you want leg drivers, write them yourself.
What you say is true about the messiness and incompleteness (and redundancy!) of many aspects of Common Lisp.
... or macros [ macros in the Lisp sense, which is a totally different thing than what most languages mean by macros] ... or CLOS's multiple dispatch)
With the benefit of hindsight, Common Lisp needs a LOT of cleanup. But as far as its feature set, all modern languages are converging on it (and have yet to get there), not the other way around.
Java and C#/CLR should receive a thorough overhaul, incorporating some of the really nifty dynamic features that Common Lisp provides (and has provided since the ancient times of computing).
(continuations, for example
Itanium uses a very advanced VLIW-esque architecture which, coupled with a sufficiently smart compiler, allows for incredible performance.
Two problems:
1. making a really _good_ compiler for such an architecture is beyond the means of computer science now and in the near future
2. we gave up back-compatibility for a fairly slow (in its own right) ia32 emulation
Actually I've been following Wine for a while, and it seems like the biggest thing holding them back was that (until recently) they didn't do any regression testing.
They'd fix one thing only to break like five or ten others.
Interestingly, now that they're moving forward with an exhaustive testing regime, they've started filling in the remaining pieces pretty fast.
And, indeed, most Open Source projects don't do much in the way of testing...
Ah, I wasn't thinking of C++ development, but thank you. It's a good link.
What I said is easily true of C development, but anyone concerned with C++ should definitely read that FAQ entry as the libg++ licensing situation is a little more complex (though not too bad; it's just important to know what to link with).
Microsoft has a patent on the process of loading an OS on such hardware.
If the hardware hits the market, Microsoft determines who can legally write an OS to run on it, via their control of the patent.
There's also the basic C runtime stubs (e.g. crt1.o), though I think that's part of glibc.
However, if you actually bother reading the licenses on the code that gets embedded by bison and gcc, special excemptions are made --
Thus, code compiled with gcc may be distributed under any license you want. Sorry, thanks for playing.
You'll need to boot from clean boot media that wasn't in the machine at the time of installation.
Otherwise you could be booting a modified kernel that would hide any changes made.
Given debuggers and disassemblers, people are going to "read" it anyway. But there's no sense in them being spiteful about withholding source.
I do not think that everyone besides commercial efforts that can afford fees like $500-$1000 US should be prohibited from developing software.
It's not like anyone else has ever produced something important.
As far as patents are concerned, Laches only applies on an infringer-by-infringer basis, and I'm pretty sure only (in effect) to back-royalties.
True only of trademarks.
Contrary to popular belief, copyrights, trademarks, and patents simply do not work the same.
Or by hiring people to kill you.
The way this should have been done is to coerce the HTML into w3c-valid HTML4, and then only pass whitelisted tags, attributes, and URL schemes.
... but they're the ones Yahoo!'s been making deals with lately) will see the potential here for interfering with dissident speech.
It might distort non-well-formed HTML, but if the HTML isn't well-formed to begin with all bets are off anyway.
I realize that would require quite a few more server resources to implement. Too bad. As it is this ill-thought-out scheme appears to stand a real chance of permanently distorting the English language.
One does wonder if the Chinese government (or any government, really
So, crimescript is double-plus ungood?
Yeah, like the ones who developed algebra [hint: al-gebra is an arabic word], or preserved and translated many of the surviving writings of the ancient world.
You can also use display: block in CSS to turn the links into block elements -- although be aware that IE doesn't quite get that right.