Follow Slashdot stories on Twitter


Forgot your password?

Comment "or any later version" (Score 1) 171 171

No business in their right mind would allow any such bull shit in any legal document that they were obligated to.
Version 4 may grant the FSF free license to:
* commercially redistribute and relicense the code as they see fit
* grant unlimited patent waivers for all code using it
* remove warranty disclaimers
* require the developers to pay each user a huge sum of money
* or whatever the hell the Fucking Stupid Fucks (or whatever FSF stands for) feel like

Its like getting a job description that has a phrase like "additional duties as required"
... clean those toilets Mr. engineer.

Comment prototyping at a bar (Score 1) 126 126

If your like-minded gang of guys are out at a bar and come up with a great idea, this method is great for banging out the initial prototype on the one laptop that someone happens to have with them.
... but then its not called Mob Programming, but gang banging.

Comment Re: Not a huge change. (Score 2) 112 112

I honestly find the whole new color palate to be way too similar to the Windows8 start area crap. Companies will eventually figure out that we have diverse visual palates the way they did with taste in the 80s, unfortunately Google missed that opportunity on this go around.

Comment lets do the math (Score 1) 56 56

Pi * r^2 gives us 3.14 * (8in/2)^2 yields 50 square inches. Assuming each chip is 1 square inch that gives us $5000/50 or $100 of savings per chip, since the wafer can be reused.

Now we need to make a few more assumptions for the rest. Assuming ~50% circuit density and similar cost, the remaining substrate would cost around $50. That's pretty significant, especially considering that many chips will be significantly smaller than a square inch.
What is also significant is the additional weight savings.

Comment Then build static right (Score 1) 324 324

If you use libraries designed with static linking in mind like musl-libc and tinyxlib, then it's not really that much. You get similar benefits to shared libraries if the program is or has recently been running... Users run programs, not libraries and shouldn't have to wait for every unused function of every dependent library to load just to run a program. What's worse is when vendors distribute alternate shared libraries with a single program so that none of the library caching occurs from other programs and the overall size increases significantly. If you are distributing multiple programs that use the same libraries, you can always create a multicall binary like busybox, toybox, dropbear and mupdf do and still do a static build that will be smaller than the overall shared build.

The gent who wakes up and finds himself a success hasn't been asleep.