Comment Re:well (Score 2) 375
Maybe he went to public school. I know I was too busy circumventing the security on the Apple II's to learn basic grammar, or punctuation.
Maybe he went to public school. I know I was too busy circumventing the security on the Apple II's to learn basic grammar, or punctuation.
Dial-up Internet killed interest in my single line BBS. (both mine and my users)
virtualization.
Sounds like a huge untapped market. I think they ought to make huge capital investments to capture the WebOS and NetBSD tablet markets.
Wolfe didn't mean it literally, but these guys do.
(actually... Wolfe wrote it in a book so isn't it literal? whatever)
I can use malloc and free in a kernel. once I've booted up to a certain point. Not a big deal at all.
If I were using C++, I can supply my own new/delete operators. I can even pass parameters to 'new' to set up special attributes.
Now I would never use C++ for a kernel, but memory allocation is not the reason why.
You are required to use C++'s type system, which is different than C's. So what you say isn't strictly true.
Another refreshing feature of OSv is that is written in C++.
It's been 40 years since Unix was (re)written in C, and the time has
come for something better.
C++ is not about writing super-complex type hierarchies (as some people
might have you believe). Rather, it allowed us to write shorter code
with less boiler-plate repetition and less chances for bugs. It allowed
us to more easily reuse quality code and data structures. And using
newly standardized C++11 features, we were able to write safe concurrent
code with standard language features instead of processor-specific
hacks. And all of this with zero performance overheads - most of C++'s
features, most notably templates, are compile-time features which result
in no run-time overhead compared to C code.
You end up taking the bad with the good. And some features in C++ are worth avoiding when you're outside of a nice big userspace runtime. Like exception handling, especially for classes that use multiple inheritance.
L4 is a microkernel and hypervisor designed specifically to run an OSlib in a virtual environment with very little overhead. It seems to me that some things about L4 are very compatible with visualization, being that most drivers in L4 operate as a virtualized environment rather than a process.
Complete socioeconomic collapse is a real possibility. Everyone seems to ignore the stakes, but to me they are very real. Even if I'm a bit uncertain on the time frame (in my lifetime? my grandchildren's lifetime?)
Not my fault they starved, if poor people would just quit being so lazy and get a job they wouldn't demand my tax dollars.
You assume your family will get free food, medical and housing. I've not seen any evidence that we're going in that direction.
They're too old and tired to becom restless and troublesome. They just want to see their grandkids and have dinner at four in the afternoon.
However robots can't do engineering. Robots can't think.
s/robots/most humans/
How will I pay for my material things? Why would someone invest money into building and operate a factory of robots only to give away free snorkles and swimfins?
You imply some kind of utopia on the horizon, but I fail to see a path leading there.
If the journalist had juicy information about us being in actual danger, it would have been introduced after the sensantialist headlines.
No, the examples were of soldiers who forgot that they had left equipment in their packs. Annoying for screeners, but nothing new and nothing alarming, at least not to me.
"Gotcha, you snot-necked weenies!" -- Post Bros. Comics