skysight-inc/HackerNews huggingface dataset:
Those kinds of errors are made trivial to handle with ? and anyhow. At least, once you’ve got a bit of practice with it. And it’s barely slower to write out; 1 character in most cases, and “Result<>” on your return type.

I ported some random Python to Rust six months ago: https://news.ycombinator.com/item?id=22712441 Here's the version I'd write today:

use anyhow::Result;
use chrono::NaiveDateTime;
use serde::Deserialize;
use serde_json;

#[derive(Deserialize)]
struct Person {
name: String,
age: u32,
hired: NaiveDateTime,
emails: Vec<String>,
}

fn main() -> Result<()> {
let data = std::fs::read_to_string("agenda.json")?;
let mut people: Vec<Person> = serde_json::from_str(&data)?;

people.sort_by(|a, b| b.name.cmp(&a.name));

for person in &people {
println!("{} ({}) - {}", person.name, person.age, person.hired);

for email in &person.emails {
println!(" - {}", email);
}
}

Ok(())
}

I learned that Chrono supports serde so I can remove my own parsing, and using ? instead of unwrap, because it's not harder and it ends up being nicer overall.

(EDIT: Ah actually, it won't recognize this specific format automatically, so I still would write the parsing code. Even then, it's still roughly in the same ballpark.)
Yes, it sucks but it's the very nature that lets tech be so flexible that gives us the bad tech experience. The things in our lives that are are very stable are the ones that do one thing and they do it very well. They do one thing and we know how to use them.

Tech, software, is so versatile that it's hard to know when to stop adding new functions and every time a new function is added we add unintended consequences.

We can start with the IC's in our gadgets. Some contain billions of different parts. It's a miracle that they even work. Add other components and software and we can see why tech sucks. Getting all those parts to work in unison all the time is next to impossible.
Yes, I have strong feelings about clipping... For many years I was using the track Moby - Inside trying to find a hifi system or headphones that could play it without sounding crap, then discovered it couldn't be because it's clipped.

And thanks but I'm happily using my patch on a pure alsa system without pulse audio, and don't really have the time to spend on adding the equivalent to yours sorry. But I'd want to if only to spread awareness about clipping - it's not just music, there are also many Youtube channels that I unsubed from because of it (I did tell them but they didn't care).

Actually preventing clipping instead just detecting it (which mine does) is a lot of work - it would need to find the loudest frequency, then find the closest band and reduce that (while loudly informing the user, and oviously with an option to control it).
This made me laugh. You read tons of scientific papers? Good for you. As anyone with an auto-immune disease and seriously interested in healing can tell you: AIP, if followed to the letter, works absolute wonders within even just a single god-damn day. But sure, read your papers... I am sure they are funded by people who have a huge interest in the result that you can cure 30% of the general population by merely changing their eating habits, as opposed to prescribing drugs that cost a fortune and going through all the hoops of the expensive medical system. Yeah, sounds really clear to me, these papers have it right.

> tend to forbid gluten intake

They don't tend to. Any diet who doesn't absolutely forbid gluten intake doesn't work. Simple as that. Gluten is one of the primary factors of developing auto-immune diseases and ergo also treating them.

> whole grain

Yeah better. Totally :). Because as opposed to white bread, whole grain bread contains all the goodies of mother nature in full force, like all the poison these flowers made against mammals to survive digestion. Bon appetite!

> get cancer from all the anti imflammatory stuff.

Totally makes sense. Yeah, eat healthy and you get cancer. You really made my day :D. You are just randomly mixing totally unrelated research results into something that is utterly wrong.

Good luck on your journey!
wait til you look at the man pages for man... it's awesome!
Because you elected someone constitutionally unfit to hold the office, a lying cheating philandering sociopath who cheated on his wife with a porn star after she gave birth, has literally dozens of serious sexual misconduct allegation etc.

Yet none of the above matters, what matters is the entire GOP been willing to cover for all off the above and worse, throwing out centuries of political norms to “win” and by doing so enable the worst president in a century to do all off the things above and worse.

This is a man who is a systemic risk to an already creaky system and I have a vested interest in the US doing well.

His inaction has led to a massive death toll, he overtly politicised a pandemic then let his family control where supplies went for political reasons.

The best thing the man could do for America is have a stroke.
Why do I then see NSGarbage all over the place in Swift code? Swift is a language facade over Objective C.
Home/End should go to the start/end of the file, not the line.

Oh you’re a Windows or Linux user? Too bad, now you need to get used to modern key bindings like OS X has.
Matthew McConaughey
It has definitely been this way _as far back as I can remember_ (at least the last two decades).

There have always been popular tools. Most of them haven't stuck around though.

Emacs has.

I wouldn't recommend using it right away though. Instead, I'd recommended accumulating some pain by using other popular editor-like,workflow-like,manipulation-like tools, because that might be the only way to appreciate what Emacs brings to the table.

(though I have to acknowledge VSCode's achievement, gaining massive adoption in what has always been a fragmented space)
Indeed, it's a hidden opportunity both ways.

While a dismaying proportion of companies seem to have surrendered to the whiteboarding / leetcode craze, a sizable number have not (or have outgrown it) -- and these tend to be better to work for ways you'd probably expect from that fact.
> Handicap elevators , building codes, emissions standards are “authoritarian”

Safety and accessibility are human needs, and regulating markets to address those needs is a completely reasonable requirement.

Forcing product designers by legislative fiat to add a cool feature you want, on the other hand, is pretty authoritarian. Nothing is stopping you from buying a general purpose computing device right now, or building one and selling it.
Chromium crucible steel was first made in Persia
For me a "modern Emacs" would basically be Notepad++ with more advanced features and programmability. The few times i tried Emacs (and i actually used it for a bit back in the early 2000s on a crappy Pentium 1 laptop i was given - and yes, i did felt the "Eight Megabytes And Constantly Swapping" meme of the 90s, though it wasn't that bad :-P) over the years i always dislike how it just doesn't mix with the native environment at all (be it Mac OS X or Windows... Linux doesn't really have a native environment and interestingly the longest i used emacs -that laptop- was under Linux :-P). Also for some reason it always felt a bit sluggish - you'd think with faster CPUs (and Emacs not having to follow fads - unlike, e.g. browsers) it'd be faster, but it always felt sluggish to me no matter what.

In general i like the idea of Emacs: a fully programmable editor that can be extended as much as you want. I just do not like the current application of that idea.

I mentioned Notepad++ because that is the editor i'm using the last few years and i like how fast it is (it opens instantly even with hundreds of files/tabs open - that it remembers the open files from last session and remembers changes in unsaved/new files is also very useful because i use it often for taking short lived notes) and how few resources it uses (it currently only uses ~15MB with a few tends of files open). But it does feel limited with pretty much zero way to customize its behavior - it is basically someone's custom configuration over Scintilla hardcoded in an executable.

However what i really like about it is that it uses (almost) the same keybindings i've used for decades and it looks and feels like a proper native Windows application like the applications i've used for decades. It basically lets me take full advantage of all the knowledge and experience i've developed over the years instead of expecting for me to throw that away and instead spend time learn how to do mostly the same stuff in a different way. And it is also very lightweight, did i mention that? I think i did, but it deserves repeat.

(the reason i use NPP is also why i do not care about VSCode or Sublime... they both feel alien and while Sublime is supposedly fast, i do not like its UI - also i do not think it is as programmable as Emacs or VSCode, but i might be wrong there...)

Perhaps there is Notepad++-alike which is also programmable and more powerful, but i just do not know it.
Use a candleholder that includes a glass sheath. The solution has been known for a long, long time, because a major cause of flickering unprotected candles -- or even extinguishing them -- is that you walk around while holding them.
Ruby has been referred to as Smalltalk meets Perl, and the problem of dealing with other people's code is one of the main things that kept me in the past from using Perl on text processing projects. The problem of collaborating in Perl was lessened a lot by adhering to Damian Conway's Perl Best Practices. Is there anything similar for Ruby?
> Dinging it for its syntax is something that I didn't think I would ever hear.

Not just syntax, but the amount of it, and the amount of special cases in it.

> SwiftUI is not part of Swift, so 1 and 2 are not relevant

SwiftUI exposes deficiencies in the "one of the best designed languages" and shows how Swift fails to scale in complex scenarios.

(1) Shows that its design cannot cope with anything complex. You have to write clunky wrappers for `if` and `foreach` (but not for while and for, apparently), because the design of the language didn't have place for expressions. The type system cannot handle complex requirements of the library and can't provide better facilities than Java.

(2) Shows just how bad the design decisions are in the language that they all but force you to write code this way. There's syntax upon syntax with no internal consistency or actual design to figure out how they all operate with each other.

And Swift UI forces more half-baked escape hatches (like the `some` "type", like the lambda changes described in (1)) etc.

I'll just once again expose my favorite piece of code ever:

guard let self = self { return }

instead of

if self == nil { return }

This is not an "extremely well designed language". These are badly thrown together pieces of half-baked ideas.

(3) Once again shows just how badly it's designed. Or, rather, how badly the parser is designed that it can't reliably figure out what is going on. In a language that has no significant whitespace you have to care about significant whitespace. Great design.

(4) I'm faulting the design of the standard library that is only compounding the problems already present. Many languages managed to figure out standard libraries that don't make you read and write files from a string object, or need 15 lines (different every year) of code to figure out how to write/read a file. This only continues to show that very little thought is going into this project, as they are being pressured for time to deliver "something".
A modern graphite pencil is indeed something of a miracle, and needs some civilization to support its construction.

Interestingly, fabricating other writing and drawing implements requires less-than-iron-age sophistication. Charcoal, referenced in the article and used prior to graphite for many/most artistic drawings, is considerably easier to make than steel swords or graphite pencils, and has been used for drawing since the Paleolithic (and still is). Ink made from a suspension of carbon particles is only slightly less crude (needs an aqueous binder).

If you were an artist thrown into pre- or post-civilization Earth and lacked a stash of graphite pencils (but could make fire), baking some vine sticks in a small stone oven for a few hours would enable you to write or draw... if you could find something to draw on.

Back to the original article -- what I found most interesting was that my intuition about the complexity of making iron (to say nothing of steel) was way off. Some things, like charcoal, ink, and even oil paint require surprisingly small operations to fabricate[1]. I incorrectly assumed iron was in that category.

[1] Watrous, "The Craft of Old Master Drawings" https://uwpress.wisc.edu/books/1945.htm has a good discussion of how traditional drawing media were created.
Yeah playing with new Ruby is one of my favorite parts of Christmas :)
Also like: https://www.google.com/about/datacenters/locations/
>.NET went with non-standard SQL-like names (select/where) […]

Which names do you believe are standard?
No, it compares this Chinese restaurant to the hundreds or thousands of other similar businesses who bank with it, in similar markets.

No, the bank doesn't ask for receipts or stake out businesses.

If that business has a transaction profile that's out of line with the 'similar business' model, they potentially get flagged.
Or to put it another way: employees of digital publisher demand that the publisher exercise editorial power.

It's not very different from a newspaper editing its writers, and Rogan could go back to indepdently operating if the editorial isn't worth the massive exclusivity deal that Spotify pays him.
ibuffer is part of the standard distribution, it's just not called by C-x C-b by default (that's bound to list-buffers instead).
New European Bauhaus
I am more accustomed to vim than emacs.
Some things I painfully miss when using something else than vim : quick and easy shortcuts to jump around the file, delete words/blocks/parenthesis, place marks to jump between parts of one or multiple files, macros, filtering parts of the file through external command...
Rubocop and you're done. It's the first thing I'd add to any team project just because life's too short for an inconsistent codebase.
"GraalVM Community editions are based on OpenJDK version 1.8.262 and on OpenJDK version 11.0.8."

https://www.graalvm.org/docs/getting-started-with-graalvm/
That wasn’t what I was refuting.

I was refusing the claim that what happened to assange is an example of what happens to someone who exposes corruption indiscriminately.

It sounds like you just agreed with me in that Assange was partisan, and thus cannot be an example of what the OP claimed.
Sqwok.im – open, simple, url-based chat aggregator, now with mentions
can someone help me - they went from 10M ARR (annual) to 10M integrated month over month for a year, why?
if they go, terminate the contracts. these neo-marxists of all kinds should answer to their actions.

Who the hell they think they are to decide what other to say/listen?!
I've used Emacs for around 14 years now, I rarely touch my configuration. There's lines in my config today, that I haven't changed since I first learned to use Emacs and set it up (e.g. keybindings, tab-width, etc.).

I like that kind of stability, makes it possible to move my focus away from the editor, towards the problems I'm trying to solve.
Well, ruby was able to be concurrent for a while now. It has lightweight cooperative threads, it has reactor loops. The problem was/is/will be - lack of gems that support either of them.

EventMachine was a nightmare to work on and to work with, but with fibers it and some wrappers you could write some neat code. Most library were making a lot of bad assumptions - "there is a GIL and i'm running on a full thread and also wtf are threads in general, never heard of it?"

Almost no one in ruby world thought about writing a better code to make application faster, it was always about either finding a better gem or adding more application servers. Here is the closest ruby has been towards concurrency https://github.com/igrigorik/em-synchrony guess why it never took off.

Ruby 3.0 is a first step towards having libraries being aware that they are in on fiber and not thread.
Clearly, it wasn't on earth, as porpoises are native in the water. Perhaps he had the porpoises on a water table?
I perled a bit in early 00s, and I never used any of those so-called advanced features, because it made the code totally unreadable.
I wonder what the appetite for extending the emacs "server" concept is. Treat it like an API and so that you can maintain core editor compatibility, but offer an easy way to implement UI layers that users might feel are more modern.

Could also lead to dedicated "org-mode" clients, etc.. that could leverage emacs under the hood via the API.
> Doesn’t that support my point that the higher tax states actually subsidize poorer states?

No, it doesn't, because your statement presupposes that Social Security payments disproportionately go to the poor. In practice, Social Security (and Medicare) represent welfare for the rich. Baby Boomers are the wealthiest cohort in the US[1][2]. (FTA) "For two-thirds of seniors, Social Security has detached from the program’s original mission — to eradicate senior poverty — and is now the world’s most expensive upgrade from Carnival to Royal Caribbean for Nana and PopPop."

While there are poor retirees that benefit from SS/Medicare, they represent the minority of their cohort. On average, retirees are among the richest people in the country owing to a lifetime of accrued earnings (unlike, say, college graduates). So programs like SS/Medicare that target retirees are about the furthest thing from "subsidizing the poor". Consider that Bill Gates, Ariana Huffington, and Warren Buffett all qualify for Medicare and receive SS checks.

SS/Medicare also represent about half of the Federal budget. This is exactly why you need to adjust for those programs, because when you say that the Federal budget overwhelmingly subsidizes "poor low tax States", half of that just goes to old people, who overwhelmingly live in Red, 0-tax states like Florida. It tells us nothing about the fiscal health of those states, nor their dependence on the Federal government. On the other hand, high tax blue states disproportionately suffer from poor fiscal health, owing to under-funded defined benefit pensions that are essentially insolvent.

> But, the entire point of my post was arguing against the idea that states with high taxes and limiting SALT was unfair to states that pay less in taxes.

But once you account for SS/Medicare, the distribution of net-contributors and net-takers does not cleanly correlate with high vs low state and local taxes. This means that it's an extremely inefficient way of handling the inequity. You think it's a problem that some states pay more than they take in? Then address that directly! Don't use state-and-local-taxes as a proxy for that. It's an extremely messy and ham-fisted way of solving that problem.

[1] https://www.bloomberg.com/news/articles/2016-07-12/the-riche...

[2] https://marker.medium.com/lessons-from-iowa-and-the-fallibil...
Because Swift allows interoperatability with Objective-C frameworks, such as the ones that ship with Apple's platforms. It's easy to see that Swift is not a language façade over Objective-C because you can write a type that cannot be represented in Objective-C almost trivially.
There are many ways to avoid shipping a syntax error. I suppose switching languages completely is one way to accomplish that, but you could also just.......... use a linter.
I’ve recently switched to VS Code, and the driving issue for me was really related to the popularity of the editor. Some combination of the LSP server and the chain of emacs packages to interface with that server were constantly broken. I can’t blame the maintainers, seeing as the LSP was being implemented by a skeleton crew and the various emacs packages were abandoned short of a couple heroes fixing some of the big bugs.

I still miss things like Magit, the binds from Spacemacs, the project integration from Projectile and Ivy/Helm, and more. VS Code has some other pluses too though, like a better terminal and smooth rendering / performance. I don’t see emacs getting those features without more popularity, but I hope VS Code gets the things I miss given how many people use it.
That’s not the same, that’s basically just AltGr. In X you can do ‘Compose, o, o’ → °, ‘Compose, C, o’ → ©’, ‘Compose, s, o’ → §, ‘Compose p o o’ → «a character HN doesn’t allow (U1F4A9)» and ~6000¹ other combinations. X also has a “mac” layout variant I’d like to hear a macOS user’s opinion of (haven’t ever wanted to use it myself).

[1]: ± some depending on if you count multiple ways of creating the same character, etc. Eg. ‘≠’ can be made by combining / and = in either order. Also ‘Compose, number, s’ for footnotes, ‘Compose, +, -’ → ±, ‘Compose , <, '’ → “‘”, ‘Compose, -, >’ → “→”, ‘Compose, =, >” → “⇒” are nice. And υɳⅰеηⅽоⅾе.
I will refrain from commenting on the general dismissiveness in your post, and stick to one of the points you made: "Ctrl-F" being linked to "move right" is the /standard keybinding/ on macOS.

In fact, /most/ of the "standard" Emacs keyboard shortcuts (Ctrl-F, Ctrl-B, Meta-F, Meta-B, even in some contexts Ctrl-K, Ctrl-Y) are /also/ the standard macOS keyboard shortcuts.
The C# REPL's not exactly great though. There's a lag the first time you use it and I regularly forget when you need to put a ; to end a statement or not.
I've worked in California all my life and have worked in the following industries: medical devices, scientific devices, blockchain, and plasma physics research. I am the only person I've seen use emacs. Almost every developer I've worked with either used VS Code, Visual Studio, or uVision. Everyone else used Sublime Text, Eclipse or a JetBrains IDE.

I haven't even used emacs in years so I don't even know anyone that uses it; I stick almost exclusively to Vim (and for 8 months this was my only "IDE"), PyCharm, and WebStorm.
Okay you want more? How’s about their texts with the trump campaign.

That was overtly partisan and thus their actions and exposures were not neutral exposure of all secrets, but targeted exposures with goals.

Thus again, not what the OP claimed.
At this point, Google is beyond reason and is openly hypocritical. Open source? Yes. Open platforms? No. Even if they are competing against YouTube.

Netflix and Youtube has disgusting content if not the former is now worse than LBRY and Google still gave Netflix a pass. If LBRY had the same content as Netflix and YouTube, Google would choose to ban LBRY 10,000 over, with the same reason.
Please show me just one example of such an interpreter. You chose the architecture and the operating system. I'll follow up with a C compiled native and see who's faster at doing the same thing.
But Windows IS evil...
Ruby can also be an extremely decision-fatiguing language to write code in.
I came to vim (years ago now) because I was experiencing RSI from all of the chorded keyboard shortcuts I was using in Coda. Emacs doesn't help with that, but vim does (if you `map ; :`).

Any editor feels clunky for the first week of using it, Vim and Emacs most of all. Nobody wastes the headspace in staying current on multiple editors. So I don't know that you'll ever see an objective comparison of the two. But they're both solid ways to write code, it just takes way too long to get either one dialed in to do the things we expect modern editors to do out of the box, like code completion.
Causality Podcast
To add to this excellent point; a common culprit is not using ~use-package~ correctly to lazy-load as much as you can. I use Emacs extensively for all my languages and have loads of packages installed, but the startup time is around half-a-second on a newish Ryzen laptop running Nix from a cold restart.