Forgot your password?
typodupeerror

Comment Re:Surprised (Score 5, Interesting) 109

There was plenty of interest in the beginning**, and the electric truck market really doesn't have good competition for a given price point. The problems were:

1) The price shot up heavily
2) The stats and capabilities went down
3) Musk went hard-right, and rightly or wrongly the Cybertruck became seen as a symbol of being MAGA.

These things together pushed away ~90% of prospective buyers. Combined with the fact that the Cybertruck's production line was unique, as well as being a generation back, and it made it hard for Tesla to justify owning it.

** - Including from me. Beyond the stats-for-the-price point as introduced, I liked the engineering behind the design. If you want to make it rugged, that implies a thick skin. So make it an exoskeleton to bear the internal loads. Want to maximize strength while minimizing the mass? Resist torsional loads with a braced cantilever design (the triangular rear). Which, with a retracting tonneau, creates a very long, gradual rear taper, allowing detached air (from the angles necessitated by an exoskeleton) ample time to retract and minimizing the drawn wake. On and on - from an engineering perspective, there was a lot of great stuff that appealed to me. But little of that ended up staying. The final design hangs the (thinner) exterior metal onto a frame just as dead mass. The big raft of changes led to mass growth, cost growth, and range decline (despite advancing battery tech and pricing). And of course, I'm not super eager for Elon to end up with any of my money these days. Another family member had also been interested, and also cancelled.

Comment Re:The problem probably isn't the disks (Score 1) 80

Amateurs. 640k is more than enough for anything. I've been going the opposite way.

I've been making the website favicon 640 gigabytes. It's not easy to do with a 16x16 icon, but the heft is worth the extra effort. You can feel the heft, the weight of the GB pixels flowing through your cable (if you didn't cheap out and get the wrong cable). Nothing beats that feeling of luxury.

Comment Re:Special case (Score 1) 61

That said, on my Debian/Devuan installations all these accounts with "*" and "!" have /usr/sbin/nologin or /bin/false as shell, so a login should still not be possible. Does anybody know whether that is a reliable protection against this vulnerability?

It should be easy enough to test. "sudo adduser a" then "ssh a@localhost." Carefully modify your passwd file to change the shell to /usr/sbin/nologin and try again. You should be logged out immediately.

I just tried it on Mint and /usr/sbin/nologin prevented logins.

Comment Re:The title seems kind of wrong (Score 1) 61

Look at the man page for crypt. Having it return a non-POSIX return value is/was configurable on some distros. This isn't a problem on OpenBSD, the true system.

BTW a lot of SV startups allow login with an empty password, despite a suite of unit tests. No one likes to write negative tests, so here we are.

Comment Re:Okay (Score 1) 61

The Linux kernel, ostensibly, follows the same philosophy of "you do not break userland" but in reality bugs happen all the time and this kernel philosophy actually doesn't help at all because Linux is the worst mainstream operating system for any kind of backward or forward compatibility--for some fucking reason you can't compile a static binary on most distros.

The Linux kernel is great for backwards compatibility. GNome is horrible.

IF you make a backwards incompatible change, you are giving millions of people extra work. Don't do that.

Comment Re: I've grown to be okay with Rust (Score 1) 60

Instead we get to have holy wars over whether or not it's appropriate to have a language where if the indents get screwed up the code is completely ruined, and can't be fixed by simply running it through fmt(1).

It's not appropriate. Anything that is better is useless for corporate work.

Worse is better. Falsehood is freedom. Truth is terror. Python is

Comment Re:I've grown to be okay with Rust (Score 1) 60

Unless you're writing in a text editor where you have to manage the whitespace yourself, almost any IDE will take care of it for you automatically.

It doesn't. If you try to paste code, the IDE gets confused, which doesn't happen with braces.

prevents the kind of holy war being waged to this day and wastes everyone's time when it winds up getting discussed or argued over yet again.

It doesn't. You're a moron, an idiot, and a heretic for liking syntactically significant whitespace. You are the worst kind of person. Trump probably likes whitespace. If you care so much about color, you're probably racist.

Slashdot Top Deals

A complex system that works is invariably found to have evolved from a simple system that works.

Working...