The iPods with flash like Nano were ripoffs of existing MP3 players. Wireless Charging Fingerprint sensor High-end mobile screen resolutions after Retina. Tablet Stylus
...is another crap product (at the start) that got out faster.
Overall, society gets a new concept faster. We are able to rationalize about the woes in public.
Otherwise you have "Magic Leap" where we don't know what we are going to get until we get it, and it's usually missing the mark. That's worse for investors, buyers, and society.
How is this any different from the Plasma Filaments that the Electric Universe guys have discussed for decades? They've even shown that they must connect star systems with their galaxy and connect across galaxies.
It's Linux. My servers run without GNU or any other user space even installed. DLL wrangling is over and lightweight containers are replacing distros fast. Security is a cinch when only your app and Linux is installed.
GC was hacked-on for decades to no avail (in bringing it low-level).But now here it works well (very fast, concurrent). What changed? The language spec was made very simple.
Compiling was a very tricky, slow business. Now here it's fast and relatively simple. What changed? A simpler language. Smart people who know which options to take away.
Only painfully low-level languages could work with raw memory pointers. Now we have that in 2 friendly, "default-safe" languages. What changed? Realization a lot of power comes from low-level operations.
So C & it's layered C++ will break as safer variants with the same power begin to exist.
High level languages depended on dozens of C libraries and libc. Go needs none of those. What changed? A realization this is important.
A fork of Go now runs without a kernel on bare-metal ARM. That's the right space to grow into a kernel-module-capable language. Languages aren't fast or slow, their implementations are. Go's ease of portage suggests it could show up in the kernel.
As a Go developer by day, I would like this to be an option too, but it will take significant rework on minimizing libraries and the runtime in order to fit on extremely low size installations.
Go runtime also requires an operating system. I'm very interested in removing this restriction, but it's there today.
Rust does anything in any space C can, but more safely. Light IoT will always need languages that are very power cautious, but I see that bringing a rise of CUDA IoT, or even FPGA skills.
1. Stop honoring BS US copyright law. Given enough countries, the whole copyright export concept will be in jeopardy. 2. Go open-source. $0+(local time) is always pegged to GDP.
Go's (initially) looks quite Python-like in terms of packages and memory concepts. Also message-passing is the main mechanism of concurrency. But Python's power (as well as its woes) comes from the C extensions & GIL. So to get rid of the GIL (required for serious Python performance) you've got to have a fast language replacing it that libraries can be written in that cross calls.
The language for this would also do best to resemble Python to begin with. Go seems like a most logical fit here.
SciPy & Numpy for example are now unusable (as they are in any Python interpreter that doesn't have C extensions). But GoLang has some very similar libraries already that work much faster. Porting either way will create viable, fast replacements.
You must be joking: - Phones/Tablets: 99+% on open kernels Linux & BSD. - Mainframes: PPC Linux - Supercomputing: Linux - Business apps Mostly on the cloud, running on Linux - IoT / motor-control: Hardened linux / RT Linux
Do you notice your circles shrinking rapidly?
All that's left I'm aware of is: - Game development - A few business apps that are local-intensive: CAD etc
GoLang is picking up speed too. It's the fastest growing language int TIOBE's top 20. At current acceleration, it'll have more programmers then C# by next year!
Then there's Node, Rust and even Elixir. No need for 15-year-old, slow tech anymore.
The problem with unbounded pointer vulnerabilities (stack smashing, return value changing, parameter changing) is the unboundedness of the pointer. ONLY the programmer and (for some languages) the compiler know what values are legal for a pointer offset.
Programmers aren't enough.
So I use GoLang (but Java, Rust, Node are all similar in this regard) because I know that all my pure-GoLang 3rd-party libs cannot have unbounded pointer errors. This means Go's SSL, not Go's OpenSSL wrapper. A Userspace written in entirely managed pointer languages cannot have these problems (except at the kernel level).
Other dimensions than today's price: - Inflation: What will Diesel cost in 10 years? - Politics: Will there be a consistent political climate to allow diesel to arrive from somewhere? - Availability: We could run out of oil one day. Reliable energy seems smart.
Cost of Living requires it. Businesses pay it because the area's talent has defined the computing era. A random "senior" group (read: just about anyone in SV) knows second-nature Agile, Scrum, code smell, architecture, multiple languages, tools & technologies they've used to build amazing things successfully.
A marketable product idea and a 5 - 20 SV senior engineers will usually have a high % chance of success. Investors know this. No extra layers. Meanwhile patents & novel solutions (thought leadership) emerge automatically.
Mozilla excels when there is a massive project that should be open to the world (and standardized) and is not. Besides the browser and email client, PDF.js is very significant and is integrated in 1000s of sites and products because it reads PDFs safely (as safe as the JS sandbox).
I think they should partner with Elon Musk's OpenAI effort to produce standards, software, and support. Their Project Vaani speech-to-text engine shows they are thinking this way, but lack the AI experience to do it themselves today.
Wind --> Trees
They've been messing with wind patterns for the past 100M years at-least. We've clear-cut so many that I think windmills just barely are restoring back the blockages trees have been offering since the dawn of our species.
Wasted Heat:
Either way, it's part of Earth's heat. If we could turn tons of "waste heat" into energy, we would then use the energy which creates . . . heat. We could store mountains full of batteries and it would make little difference (we would be recreating Oil-like storage). Though putting this recycled system over ocean is less wise than over low-wind desert for ecology & maintenance reasons.
Its base-project (Wine) is already a standard Microsoft themselves uses for compatibility testing. As they cover more APIs, I suspect they will start closing-in, especially since they only implement what works and ignore projects Microsoft failed at (old mobile OS versions, for example). With Chakra-Core and other Microsoft open-source pieces, they can collect gains they don't even need to build.
There may even be a time Microsoft sees this open-source project with "clean" C/C++ code superior to the multi-GB amassment of questionable binaries they add to devices today.
Slashdot Mirror
Apple was frequently a late-mover:
The iPods with flash like Nano were ripoffs of existing MP3 players.
Wireless Charging
Fingerprint sensor
High-end mobile screen resolutions after Retina.
Tablet Stylus
How: C, C++, and Java making errors easy.
It's early days & we trade for speed with grossly unsafe situations. It's like a shortcut though a warzone.
We need contacts requiring:
- provably zero: buffer overflows, use-after-free, double-free, stack overflows, memory race conditions
- Malloc failures must crash if unrecoverable.
Then we could begin to have software with greater peace of mind.
Rust does this, as does JavaScript without extensions. Go does most and can be limited to a subset that does all. Some provers exist for C subsets.
...is another crap product (at the start) that got out faster.
Overall, society gets a new concept faster. We are able to rationalize about the woes in public.
Otherwise you have "Magic Leap" where we don't know what we are going to get until we get it, and it's usually missing the mark.
That's worse for investors, buyers, and society.
How is this any different from the Plasma Filaments that the Electric Universe guys have discussed for decades?
They've even shown that they must connect star systems with their galaxy and connect across galaxies.
Sure they'll come back up, but if there's a pass of this machine every 3 days, it'll eventually kill it.
It's Linux. My servers run without GNU or any other user space even installed. DLL wrangling is over and lightweight containers are replacing distros fast. Security is a cinch when only your app and Linux is installed.
GC was hacked-on for decades to no avail (in bringing it low-level).But now here it works well (very fast, concurrent).
What changed? The language spec was made very simple.
Compiling was a very tricky, slow business. Now here it's fast and relatively simple.
What changed? A simpler language. Smart people who know which options to take away.
Only painfully low-level languages could work with raw memory pointers. Now we have that in 2 friendly, "default-safe" languages.
What changed? Realization a lot of power comes from low-level operations.
So C & it's layered C++ will break as safer variants with the same power begin to exist.
High level languages depended on dozens of C libraries and libc. Go needs none of those.
What changed? A realization this is important.
A fork of Go now runs without a kernel on bare-metal ARM. That's the right space to grow into a kernel-module-capable language. Languages aren't fast or slow, their implementations are. Go's ease of portage suggests it could show up in the kernel.
lol! Near-40 here & considering the same!
Better answer: Castro St, Mountain View
Use your cleverness to launch a great idea with a small team of experts. You'll need to buy your own lunch & gym membership though.
This always happens during times of intensive solar flares.
I'm thinking the Electric Universe's answer is right.
I use neither. When I hit save, it auto-reformats. I'm not sure really which it becomes.
Checking...
Tabs. Oh well, it's not me writing them.
As a Go developer by day, I would like this to be an option too, but it will take significant rework on minimizing libraries and the runtime in order to fit on extremely low size installations.
Go runtime also requires an operating system. I'm very interested in removing this restriction, but it's there today.
Rust does anything in any space C can, but more safely.
Light IoT will always need languages that are very power cautious, but I see that bringing a rise of CUDA IoT, or even FPGA skills.
Heavy IoT will always be flavor-of-the-month.
1. Stop honoring BS US copyright law. Given enough countries, the whole copyright export concept will be in jeopardy.
2. Go open-source. $0+(local time) is always pegged to GDP.
Go's (initially) looks quite Python-like in terms of packages and memory concepts. Also message-passing is the main mechanism of concurrency.
But Python's power (as well as its woes) comes from the C extensions & GIL. So to get rid of the GIL (required for serious Python performance) you've got to have a fast language replacing it that libraries can be written in that cross calls.
The language for this would also do best to resemble Python to begin with. Go seems like a most logical fit here.
SciPy & Numpy for example are now unusable (as they are in any Python interpreter that doesn't have C extensions). But GoLang has some very similar libraries already that work much faster. Porting either way will create viable, fast replacements.
You must be joking:
- Phones/Tablets: 99+% on open kernels Linux & BSD.
- Mainframes: PPC Linux
- Supercomputing: Linux
- Business apps Mostly on the cloud, running on Linux
- IoT / motor-control: Hardened linux / RT Linux
Do you notice your circles shrinking rapidly?
All that's left I'm aware of is:
- Game development
- A few business apps that are local-intensive: CAD etc
Anything else?
GoLang is picking up speed too. It's the fastest growing language int TIOBE's top 20. At current acceleration, it'll have more programmers then C# by next year!
Then there's Node, Rust and even Elixir. No need for 15-year-old, slow tech anymore.
The problem with unbounded pointer vulnerabilities (stack smashing, return value changing, parameter changing) is the unboundedness of the pointer. ONLY the programmer and (for some languages) the compiler know what values are legal for a pointer offset.
Programmers aren't enough.
So I use GoLang (but Java, Rust, Node are all similar in this regard) because I know that all my pure-GoLang 3rd-party libs cannot have unbounded pointer errors. This means Go's SSL, not Go's OpenSSL wrapper. A Userspace written in entirely managed pointer languages cannot have these problems (except at the kernel level).
Other dimensions than today's price:
- Inflation: What will Diesel cost in 10 years?
- Politics: Will there be a consistent political climate to allow diesel to arrive from somewhere?
- Availability: We could run out of oil one day. Reliable energy seems smart.
Cost of Living requires it. Businesses pay it because the area's talent has defined the computing era. A random "senior" group (read: just about anyone in SV) knows second-nature Agile, Scrum, code smell, architecture, multiple languages, tools & technologies they've used to build amazing things successfully.
A marketable product idea and a 5 - 20 SV senior engineers will usually have a high % chance of success. Investors know this. No extra layers. Meanwhile patents & novel solutions (thought leadership) emerge automatically.
Mozilla excels when there is a massive project that should be open to the world (and standardized) and is not. Besides the browser and email client, PDF.js is very significant and is integrated in 1000s of sites and products because it reads PDFs safely (as safe as the JS sandbox).
I think they should partner with Elon Musk's OpenAI effort to produce standards, software, and support. Their Project Vaani speech-to-text engine shows they are thinking this way, but lack the AI experience to do it themselves today.
But it's not a personal computer with Windows 10, it's a Windows 10 appliance. False advertising!
It's quite easy to get an OPS position in SF. They should just get out of there early.
Oracle (for whatever reason) has no community trust. MariaDB and other forks are getting common use and will likely see the same shift.
Wind --> Trees
They've been messing with wind patterns for the past 100M years at-least. We've clear-cut so many that I think windmills just barely are restoring back the blockages trees have been offering since the dawn of our species.
Wasted Heat:
Either way, it's part of Earth's heat. If we could turn tons of "waste heat" into energy, we would then use the energy which creates . . . heat. We could store mountains full of batteries and it would make little difference (we would be recreating Oil-like storage). Though putting this recycled system over ocean is less wise than over low-wind desert for ecology & maintenance reasons.
As for dams, yes they're not so great.
Its base-project (Wine) is already a standard Microsoft themselves uses for compatibility testing. As they cover more APIs, I suspect they will start closing-in, especially since they only implement what works and ignore projects Microsoft failed at (old mobile OS versions, for example). With Chakra-Core and other Microsoft open-source pieces, they can collect gains they don't even need to build.
There may even be a time Microsoft sees this open-source project with "clean" C/C++ code superior to the multi-GB amassment of questionable binaries they add to devices today.