And were they any good?
My car runs Android Automotive^1 on an Intel Atom and performance is trash. I would hate to have a phone on the same platform.
^1 As in, the car runs Android directly, not Android Auto running from a phone.
And were they any good?
My car runs Android Automotive^1 on an Intel Atom and performance is trash. I would hate to have a phone on the same platform.
^1 As in, the car runs Android directly, not Android Auto running from a phone.
What are you going on about? Have you ever ridden in one of these?
They do have these buttons…
I see. Yeah, obviously the world only has 3 spatial dimensions, so you can’t represent 4D data spatially.
My general point is that we have additional senses that we can use to represent additional dimensions. And that totally counts as “visualization”.
And it is not possible to “visualize 4D”
Sure it is.
And that’s not even counting projection. All the time we interact with 3D data that’s projected to 2D (almost every photo you’ve ever looked at). There are similar ways to project 4D to 2D.
(Not defending the video or anything, just pointing out that visualizing higher dimensions is something we know about for ages.)
Yeah, I think so.
At first, Xockets sounded like a legit tech company to me. But a closer look at their website reveals that it’s actually run by a bunch of patent attorneys.
+1
From an order of magnitude perspective, the max is terabytes. No “normal” users are dealing with petabytes. And if you are dealing with petabytes, you’re not using some random poster’s program from reddit.
For a concrete cap, I’d say 256 tebibytes…
Where I work, everything is on IPv6. Both the infrastructure for the software services that we run, and our own internal corporate network.
My ISP also provides publicly routable IPv6 prefixes over DHCP. Any layman in my city with this ISP will be on IPv6 by default.
I also use IPv6 for my LAN.
Like, it’s just kind of the default in my neck of the woods…
[S]hareholders said they learned that CrowdStrike’s assurances about its technology were materially false and misleading when a flawed software update disrupted airlines, banks, hospitals and emergency lines around the world.
I don’t see how they can make this argument.
Falcon is a kernel module. When kernel modules fuck up, you get kernel panics.
Sure, the layperson may not know enough about computers to recognize this, but it’s a basic enough fact about operating systems that an investor in a company like this should take the time to learn. It’s not like they hid that fact.
If you invested in a company without knowing how their product works, that’s on you.
Maybe.
Linux won because it worked. Hurd was stuck in research and development hell. They never were able to catch up.
However, Linus’s kernel was more elaborate than GNU Hurd, so it was incorporated.
Quite the opposite.
GNU Hurd was a microkernel, using lots of cutting edge research, and necessitating a lot of additional complexity in userspace. This complexity also made it very difficult to get good performance.
Linux, on the other hand, was just a bog standard Unix monolithic kernel. Once they got a libc working on it, most existing Unix userspace, including the GNU userspace, was easy to port.
Linux won because it was simple, not elaborate.
You talk about “non-absolutist,” but this thread got started because the parent comment said “literally never.”
I am literally making the point that the absolutist take is bad, and that there are good reasons to call unwrap in prod code.
smdh
Fair. But unwrap versus expect isn’t really the point. Sure one has a better error message printed to your backtrace. But IMO that’s not what I’m looking for when I’m looking at a backtrace. I don’t mind plain unwraps or assertions without messages.
From my experience, when people say “don’t unwrap in production code” they really mean “don’t call panic! in production code.” And that’s a bad take.
Annotating unreachable branches with a panic is the right thing to do; mucking up your interfaces to propagate errors that can’t actually happen is the wrong thing to do.
Unwrap should literally never appear in production code
Unwrap comes up all the time in the standard library.
For example, if you know you’re popping from a non-empty vector, unwrap is totally the right too for the job. There are tons of circumstances where you know at higher levels that edge cases defended against at lower levels with Option
cannot occur.
They can’t even be punished. robots.txt
is just a convention, not a regulation. It’s totally not enforceable.
The only legal framework we have is copyright law. Those who oppose this behavior will have to demonstrate copyright violation, and that may be difficult to do since the law hasn’t caught up.
This comment is copyrighted by me and licensed to the public under the terms of the CC-BY-NC-SA 4.0. If you intend to use this comment for commercial purposes, you must secure a commercial license from me, which will cost you a lot of money. If you violate the terms of the CC-BY-NC-SA 4.0 without securing an appropriate license, I will send my army of lawyers that I totally definitely have to defend my copyright against you in court.
orlp invented PDQSort and Glidesort. He collaborated with Voultapher on Driftsort.
Driftsort is like a successor to Glidesort.
Glidesort had some issues that prevented it from being merged into std, and which are addressed in Driftsort. IIRC it had something to do with codegen bloat.
Zsh
No plugin manager. Zsh has a builtin plugin system (autoload
) and ships with most things you want (like Git integration).
My config: http://github.com/cbarrick/dotfiles
Exactly.
My take is that the issue isn’t with tmpfiles.d, but rather the decision to use it for creating home directories.
Huh. This got me curious.
Yes, I did just type a bare URL. Every mature markdown parser I’ve used turns this into a link, and appropriately handles trailing punctuation.
So I went to the spec, and it’s explicitly called out that this is not an autolink. Autolinks must be explicitly surrounded with angle brackets <>
.
So yeah \shrug.
https://spec.commonmark.org/0.31.2/#autolinks
Edit to be clear: This means that both of our markdown parsers are wrong relative to the commonmark spec. But I’ll argue that if a parser is going to attempt to autolink this, then handling trailing punctuation is better than not.
What could Twitter possibly offer to make me switch banks?
What could Twitter possibly offer to make me switch brokers?
What could Twitter possibly offer to make me switch from Venmo and PayPal?
Which Americans are not in a similar position?
X Payments is doomed to fail. He missed the boat. The market is already saturated, and they’ve lost all brand loyalty.