Hemospectrum

The keyword was always there, but it meant something different. In modern C++, it tells the compiler to perform type inference. In B, it told the compiler to dynamically allocate a variable on the stack, as opposed to assigning it a static address, or a register.

It's a BASIC dialect. The syntax isn't arbitrarily different from C#. It was inherited from previous incarnations of this project, going back to the Amiga days.

https://en.wikipedia.org/wiki/Blitz_BASIC

Musical instruments aren’t too cheap either. Drummers and guitar players can get good stuff secondhand, but most synthesizers will run you way more than a mid-range MacBook and a copy of Logic. God help you if you need a piano...

It does increase naturally. The catch is: If the overall gene pool is too small, the viability of successive generations will decrease faster than the rate at which the gene pool can expand.

Gundam was always about societies experiencing large-scale changes that no individual person has a handle on, and the struggles of people who try to make a difference anyway. In that sense, it's comparable to The Expanse, and the "magical" elements serve more or less the same purpose.

Planetes, on the other hand, isn't much like either of these. Its subject matter is intensely personal, and even when the characters occasionally get involved in high-stakes situations, it's less to do with changes in society (which occur much more slowly) and more to do with someone turning their small-scale private difficulties into everybody else's problem. The political elements intrude for a while and disappear again, and I don't remember them nearly as well as the bits about a lost watch, or a marriage proposal.

In a nutshell, if Gundam and The Expanse need magic because they're larger-than-life, Planetes has no use for it, because it's exactly-the-same-size-as-life.

It might be better, certainly, but I can’t imagine it would be more popular. Languages ride to popularity on the backs of platforms, either commercial or educational. It has very little to do with their features.

> Do public infrastructures and services cost more in inflation adjusted dollars and achieve less? That's a pretty significant claim which needs serious evidence.

Yeah, it would have been nicer if claims like this within the article had links to supporting discussions of some kind. On this topic, at least, I've seen numerous discussions on HN, so I googled a little bit and found some articles that look familiar:

https://fee.org/articles/the-unbearable-truth-about-infrastr...

https://news.ycombinator.com/item?id=22122460

EDIT: Replaced the second link with an HN discussion about it from earlier this year. Couldn't find one for the other article.

From what I'm seeing, most of the people asking are artists and musicians, and the apps they use are more RAM-hungry than the OS itself or the bundled Apple apps. However, I'm not sure what specific apps those are. Maybe they're ports from Windows, and their iOS-native competitors can make better use of GPU and ML hardware acceleration APIs, since those seem to be strengths of the A14 SoC.

The internet is erupting in a chorus of "How much RAM?" but Apple seems to be keeping quiet about that. Maybe we'll find out from an iFixit teardown.

The popularity of C++ took off at a time when its competition was C. Not modern C, but C89 and older. Oceans of ink have been spilled describing the quality-of-life improvements that early C++ made over contemporary C. It is only with hindsight that we see how flawed these improvements were, and how other languages might achieve them with more elegance (and fewer corner cases that constantly explode in your face).

This looks nice and detailed.

If I had one wishlist item, it would be the exact board dimensions. Occasionally there are boards smaller than what their form factor specifies. For example, the Asus PRIME A320M-K, at 226mm by 221mm, will fit in a CM NR200, which is nominally a Mini-DTX case.

According to IRC rumors, automatic updates are delayed for a bit after the release is announced. Not sure if this is due to CDN replication or some other issue. At any rate, you can get the update faster by downloading and installing it manually.

It depends on how long, and how often, you burn those engines. If you’ve got a big torch that can sustain a large fraction of one gee for weeks or months, and your fuel is cheap enough, why turn it off at all? On the other hand, if it’s only good for a big push at the beginning and end of your trip, and you’ll spend the whole time coasting, spin is absolutely the way to go.

The Expanse, as mentioned in other comments, showcases both these designs. Most ships fly a brachistochrone trajectory with a mid-point “flip and burn,” but the Mormons’ giant colony ship has a drum.

The result screenshots are pretty cool-looking... and I personally wouldn’t board any of these spacecraft! The decks should be stacked along the main engines’ thrust vector, so the acceleration doubles as a source of artificial gravity.

Maybe I should open an issue...

Zoom usage has skyrocketed in the past few weeks among quarantined users. Plenty of them are sick of hearing about the virus itself. Covering Zoom is a way for news outlets to reach that audience.

As it happens, there are plenty of bad things to say about Zoom, which has hit headlines multiple times in the past year for security problems and various other dick moves.

Lots of people have migrated. Some have migrated back. Neovim is developing at a good pace, porting features from some of its GUI clients to the TUI. Some of the features that set it apart have been reimplemented and landed in upstream Vim. As such, plenty of plugins are portable across both editors. Personally, I’ve stuck with Neovim since I switched.

This style of keyboard is called "40%" and, just as you would press shift+1 to input an exclamation mark, they're invariably set up with additional modifier keys (or chorded sequences) to input the values of all the missing keys.

It's hard to say exactly how this one is configured, because it looks like a custom layout. The kit can be found here: https://5z6p.com/products/plaid-through-hole/

Some languages (eg. Swift, Rust, Kotlin; Dart is working on it) allow you to implement "extension methods" separately from the actual type definitions, even when the type in question is from another module/library. It's as if they're codifying the view that "OOP" is all a matter of syntactic convenience, and can't help us with the really hard problems.

I was honestly looking forward to an explanation of what utensils to use, and what sort of wines to pair them with. As it turns out, lignin is not especially nutritious to human beings, so perhaps “read books” would be a more helpful choice of words. Obviously the implication is that you only read a book once, but I’m not sure I can get on board with that.

I think I’ll go reread Red Dragon, which has a lot to say on the topic of consuming.

That's a "computed property," ie. a getter method pretending to be an instance variable.

There's data on fraud and chargeback rates for adult-content-related credit card payments. They're much higher than for other goods and services. Major payment processors have blanket bans on such transactions, and will often refuse to do business with companies that don't have such bans. And you can't buy ads if you can't pay for them.

It's one thing to draw some widgets. That's the "easy" problem (to borrow some AI jargon).

It's totally another thing to specify how these widgets read and write the model in which the business logic is encoded. If you want to animate transitions between valid model states, it all gets ten times as complicated. And then when you try to make it performant by eliminating redundant redraws, it becomes an even bigger mess.

There is no simple and obvious solution that tackles all of the above. The reactive UI model (not just Flutter, but all React-like frameworks) is an ongoing attempt to do a better job of all of it, with varying success. Existing UI toolkits, before the introduction of this model, were not designed for it. They were built on the assumption that the future would be a giant object graph caught in a tangle of callback methods. If you want to make a reactive UI populated by native widget objects, you have to figure out how to plumb all their mutable state back into the reactive model. That's an enormous investment of labor. Writing a new toolkit from the ground up is a huge amount of work in absolute terms, but in relative terms it's the easy way out.

Thanks, that was a dumb mistake on my part... And a mistake I wouldn’t make if I could rely on a third party to build and run a datacenter for me. I’m not interested in building a datacenter.

Are you planning to run your own T1 lines to the backbone when you're building your own datacenter to host one video?

We don't "need" them, sure, but we live in a society. We're supposed to be able to delegate work to others who specialize in doing it.

It refers to Entity-Component-System, an architectural design pattern (like Model-View-Controller) that uses composition instead of inheritance to define the behavior of entities in a simulation.

I upvoted this for the slick hypercomic intro before the article body, and now I’m going back to read the rest of the article. While reading it I might decide it’s a crappy article, but it still has a neat intro, and other people seeing it and writing better articles (possibly including myself in this, someday) might be inspired by it to make more neat intros. I have to remind myself all the time that doing something in isolation is not much different from doing nothing at all, and therefore, presentation is important.

> Isn't brew native?

It's third-party. Tailor-made for MacOS, but not included with the Apple developer tools.

Neat. This looks a lot like GHC’s rewrite rules (used to define loop fusion optimizations, among other things) except that Haskell doesn’t have to worry about side effects quite as much and the whole system is simpler as a result.

Yep. Most of the "French" words in English (beef, butcher, danger, very, act...) actually come from dialects brought over by the Normans when they conquered England in 1066. That's closer on the timeline to Latin than modern French.

In a nutshell: Too much pointer chasing. C# actually does much better than Java here, with its features for working with user defined value types, but it could still improve by a lot.