Agreed almost completely. Parallel initialization is important, so is reducing the kernel size (for some situations), but growing initrd is a bad idea. I'd parallelize by blocking callers (to an API that requires more boot-up) at the OS until the setup & call is done. That way almost nothing changes and if someone's interested enough to profile their code then they can re-arrange something. Then later if Async/Notify APIs are in-demand they could be added.
Funny, I worked for IBM Support where major tools had a password char limit of 8. If IBM Consulting ever found IBM Engineering, the effects would be astounding.
Look at Apple? No iOS Flash, Little attempt at interoperability outside their walls. No competing apps.
There isn't a "no hassle" file format except maybe a Google docs link (as it adjusts for various browsers).
It's a nice device, but with PDF Annotation & OneNote both available on Android. It has competition. And you lose anti-virus, gain a future OS upgrade (if you go with a top name), have a thinner, cooler (temperature) device with days of instant standby. All for about the same cost, or less if you can handle a smaller screen size (which Android works sufficiently with).
It lacks search (a critical failure for me). With mobiles in various states, I'd prefer optimizing the original site for easier mobile use instead of a new site.
Thank you. That's exactly what I see too. I'm hoping for the beginning of the end for Wall St.
Long-term thinking is good for the company & its employees. Privatization ends the race-to-the-bottom talent drain/churn.
The current system has survived due to humanity's high pain tolerance (for low quality, wages, etc), but the next generation of Americans know how nice employees in (some) other countries are treated. There's fairly high animosity already among them when it comes to working for corporations when they've seen SOPA and know where corruption money comes from.
There's a high-feature option (iOS) and a high-ubiquity (low cost sometimes) option (Android). Copycats here won't get far no-matter how much they finance it unless they find a crack in the wall (like what Verizon's Droid campaign did for Android). For example:
- High-feature increasingly means Cloud (Maps, Siri, etc), an Apple weak point
- Carriers doing updates slowly makes for unsafe Android phones. A safer (or centrally-updatable) base may be desired in a low-cost phone. (Firefox-phone Advantage)
- The first phone onto a new technology that's somehow hard to cope with?
- - Wireless Mesh as the primary communication channel (vs Internet or carrier channels)
- - Robotics (somehow)
- - Screen-less phones, or Goggle-phones
- - Native emulation (simulation?) of multiple phone OSes
For people who need to do Real Work in Cloud apps. Email, IM, Accounting, various Management, Online Education (outside CS), Data Entry, Blogging, Web Content Creation & more are all available on a device no-one is going to screw-up easily. They're high reliability (low setup & virus risk) systems for people who don't mind being limited to just the Internet.
The wide variety of platform dev targets is causing anything & everything with a UI to consider a Web/Cloud app interface (for all the devices your regular development missed).
Research NanoSolar / Thin-Film Solar. It's made from only the most common materials on Earth in a relatively-simple process (no clean-room or silicon wafers).
Math? 10,000 years old (at-least) Architecture? 6,000 years old (at-least) Software Design? 50 years old (at best). The other fields grew because of vast peer review of shared knowledge of experimentation & improvement. Of software design, only open-source can grow that way. If you want to avoid blatant stupidity, go open.
Those businesses could be labelled all those things. Facebook at start-up needed the savings of the Linux stack. Since then, Facebook has hired many open-source-trained engineers & contributed back various open technologies. Software was originally a freebie to sell hardware.
There could easily, soon be no "Open-only companies" while open-source would continue to grow inside each company that recognizes its value even to the extent that their business model depends on it.
Looks great until the last paragraph. Facebook wouldn't have gotten off the ground unless PHP, Apache, Linux, & MySQL were all very available for initial development. Had it needed ramp-up & investor buy-in, it would have been taken from the original developers.
Google's cloud services are much cheaper than the competition because of unification which was possible because all code could use the same open foundation (IBM, even Microsoft could not).
Twitter's cost & proprietary competition, what?
Farming in 1900 with tractors was "delegating everything to machines". We went on to have services like psychologists (good luck automating that) & yoga instructors (ha!). New inventions & discoveries created new industries (Computing, Internet, Statistics). Vast world-wide data sources (on food, healthy practices, habits, cultures) are being stitched together, examined, & even monitored.
If I have a huge change, like Wayland replacing X11 for the default apps. Where would that go?
Previously, it would go best into LTS+1 or LTS+2 (if LTS was a "long" freeze). The current release cycle allows the best flexibility for change.
Wine's DirectX to OpenGL translator presents DirectX-capable video cards to Windows VMs on Linux. Valve can use it as a library for a closed-source Linux app could and no one would know unless you reverse-engineered the game.
And with Valve making a console, you'll never know it's a "fiddly" Linux system underneath.
It's an open stack that's withstood years of security hardening already with a well-tested sandbox (Gecko Javascript). Also the lack of app updates every evening (like the other 3) will help keep data usage down to what's used. There is enough new & different in this phone that I could see it going (low-price) places where even Android can't reach.
Slashdot Mirror
Last I read, KMS allows crash messages. I'd assume similarly that they'd allow pre-userspace messages as well.
Agreed almost completely. Parallel initialization is important, so is reducing the kernel size (for some situations), but growing initrd is a bad idea. I'd parallelize by blocking callers (to an API that requires more boot-up) at the OS until the setup & call is done. That way almost nothing changes and if someone's interested enough to profile their code then they can re-arrange something. Then later if Async/Notify APIs are in-demand they could be added.
Funny, I worked for IBM Support where major tools had a password char limit of 8. If IBM Consulting ever found IBM Engineering, the effects would be astounding.
Look at Apple? No iOS Flash, Little attempt at interoperability outside their walls. No competing apps.
There isn't a "no hassle" file format except maybe a Google docs link (as it adjusts for various browsers).
It's a nice device, but with PDF Annotation & OneNote both available on Android. It has competition. And you lose anti-virus, gain a future OS upgrade (if you go with a top name), have a thinner, cooler (temperature) device with days of instant standby. All for about the same cost, or less if you can handle a smaller screen size (which Android works sufficiently with).
History favors open information & sharing. Patents originally helped this by reducing Trade Secrets, but now encourage hidden processes.
It lacks search (a critical failure for me). With mobiles in various states, I'd prefer optimizing the original site for easier mobile use instead of a new site.
Thank you. That's exactly what I see too. I'm hoping for the beginning of the end for Wall St.
Long-term thinking is good for the company & its employees. Privatization ends the race-to-the-bottom talent drain/churn.
The current system has survived due to humanity's high pain tolerance (for low quality, wages, etc), but the next generation of Americans know how nice employees in (some) other countries are treated. There's fairly high animosity already among them when it comes to working for corporations when they've seen SOPA and know where corruption money comes from.
There's a high-feature option (iOS) and a high-ubiquity (low cost sometimes) option (Android). Copycats here won't get far no-matter how much they finance it unless they find a crack in the wall (like what Verizon's Droid campaign did for Android). For example:
- High-feature increasingly means Cloud (Maps, Siri, etc), an Apple weak point
- Carriers doing updates slowly makes for unsafe Android phones. A safer (or centrally-updatable) base may be desired in a low-cost phone. (Firefox-phone Advantage)
- The first phone onto a new technology that's somehow hard to cope with?
- - Wireless Mesh as the primary communication channel (vs Internet or carrier channels) - - Robotics (somehow)
- - Screen-less phones, or Goggle-phones
- - Native emulation (simulation?) of multiple phone OSes
For people who need to do Real Work in Cloud apps. Email, IM, Accounting, various Management, Online Education (outside CS), Data Entry, Blogging, Web Content Creation & more are all available on a device no-one is going to screw-up easily. They're high reliability (low setup & virus risk) systems for people who don't mind being limited to just the Internet.
The wide variety of platform dev targets is causing anything & everything with a UI to consider a Web/Cloud app interface (for all the devices your regular development missed).
Starcraft 2 (around 2010) works well, and its upcoming expansions will most-likely continue to.
USB Flash Drive:
32GB - $17.98 ($5.60 per 10 gigabytes)
If you're storing just an OS image, why waste $30?
Research NanoSolar / Thin-Film Solar. It's made from only the most common materials on Earth in a relatively-simple process (no clean-room or silicon wafers).
It works oppositely: If you have "common carrier" status then any copyright infringement claim can be denied.
Math? 10,000 years old (at-least)
Architecture? 6,000 years old (at-least)
Software Design? 50 years old (at best).
The other fields grew because of vast peer review of shared knowledge of experimentation & improvement. Of software design, only open-source can grow that way. If you want to avoid blatant stupidity, go open.
Read about Onion routing
Those businesses could be labelled all those things. Facebook at start-up needed the savings of the Linux stack. Since then, Facebook has hired many open-source-trained engineers & contributed back various open technologies. Software was originally a freebie to sell hardware. There could easily, soon be no "Open-only companies" while open-source would continue to grow inside each company that recognizes its value even to the extent that their business model depends on it.
Then systematically determine how to eliminate these problems.
I see Bochs for Android (QEMU) running WinXP on YouTube. That's really the best tool I think you'll find.
Looks great until the last paragraph. Facebook wouldn't have gotten off the ground unless PHP, Apache, Linux, & MySQL were all very available for initial development. Had it needed ramp-up & investor buy-in, it would have been taken from the original developers.
Google's cloud services are much cheaper than the competition because of unification which was possible because all code could use the same open foundation (IBM, even Microsoft could not).
Twitter's cost & proprietary competition, what?
Farming in 1900 with tractors was "delegating everything to machines". We went on to have services like psychologists (good luck automating that) & yoga instructors (ha!). New inventions & discoveries created new industries (Computing, Internet, Statistics). Vast world-wide data sources (on food, healthy practices, habits, cultures) are being stitched together, examined, & even monitored.
If I have a huge change, like Wayland replacing X11 for the default apps. Where would that go?
Previously, it would go best into LTS+1 or LTS+2 (if LTS was a "long" freeze). The current release cycle allows the best flexibility for change.
Wine's DirectX to OpenGL translator presents DirectX-capable video cards to Windows VMs on Linux. Valve can use it as a library for a closed-source Linux app could and no one would know unless you reverse-engineered the game.
And with Valve making a console, you'll never know it's a "fiddly" Linux system underneath.
It's an open stack that's withstood years of security hardening already with a well-tested sandbox (Gecko Javascript). Also the lack of app updates every evening (like the other 3) will help keep data usage down to what's used. There is enough new & different in this phone that I could see it going (low-price) places where even Android can't reach.
Agreed. XBox culture runs Microsoft (Metro is proof). WinRT tablets are primarily XBox portables. MS will diversify under the XBox influence.