skysight-inc/HackerNews huggingface dataset:
I agree with what you say, except for "C coders like C to the exclusion of all else".

I doubt very much that there are many C coders who like the C language.

I had liked very much C around 1990, when I could use for the first time the Microsoft C compiler and the Borland Turbo C compiler.

Previously I did not have access to programming languages better than Cobol, Fortran, Basic or Pascal. In comparison with any of those, programming in C was much more enjoyable.

However, later, after better languages became available, I had no reason to continue to like C.

Despite that, I continue to program frequently in C, because there are still cases when it remains the best choice, for various reasons having nothing to do with the quality of the language, i.e. mainly for embedded computers or kernel drivers.

In any case, the C language will always remain on the list of languages important in the history of programming languages, independently of how many programmers happened to use C or to like it, because of a couple of valuable innovations: the "continue" statement and the distinct operators for the McCarthy "and" and "or" and for the bit string "and" and "or" (though it would have been better if single characters would have been used for McCarthy operators and double characters for the bit string operators).

(A few other innovations that are sometimes attributed to C had actually been introduced in the language B, the predecessor of C, or in the language BCPL, the predecessor of B, or in the language CPL, the predecessor of BCPL.)
When you code go by sticking to the standard lib like that, that the friction of updating becomes as smooth as compiling with the new version and deploying. Really quite sweet.

You -CAN- go the route of using a well supported, well maintained library but I have seen some code rot on larger projects in the go code ecosystem for stuff that tried to include more batteries.
That's often true when people are downloading stuff for servers but how many are downloading on an M1 Mac and then moving it to an Intel Mac? It seems like an extreme edge case.
> Your experience isn’t germane to this situation.

I've been seeing more and more of this rude dismissal of other comments. They're discussing the general topic at hand by offering their experience. Your snarky reply degrades the conversation significantly more than them broadening the conversation.

Less of this, please.
>we could have a zero Covid planet

No we couldn't have. It's never been done in history and is probably impossible to do.
I made a free web app to perform functions like DNS lookups, port checks port scans, IP Information gathering, hash generation, blacklist checks, subnet calculation and more..

saves me some time in the infosec/net-sec space; good for those who are terminal/scripting averse..
While this is true when the homes are isolated, in many cases there are power grids, and thus in principle can get their (Arctic circle?) winter power from Mexico or Italy (I don’t know where you live).

I think the small number of exceptions are, even collectively, even long term, not problematic to fuel chemically.

What kind of insulation do you have? I keep expecting aerogel on sites like this.
> Verbosity in Java is a big one. IDEs fill it in for you. It doesn't slow you down.

It most definitely does! Perhaps not when writing code. But it does take longer to read/scan verbose code. I'd also argue many kinds of refactoring are made slower by verbosity.
Why not? If you worn it until it needs repair you’re probably fond of it.
> Most of the macro-op-fusion suggested are quite trivial and have already been implemented

In which chips, and how much of a win are they?
Only if that's considered to be in the child's best interests. For example, older children can't be given away without their consent, fathers generally can't terminate their responsibility without the mother's consent, and it must be done in a manner that protects the child (not simply abandoned).
> Originally (pre-ECMA days)..

JS appeared in Dec 95 and the first ECMA spec came in June 97, so that's a pretty narrow window. But it's certainly true that ASI style (omitting semicolons) was relatively rare before, say, 2010-2014 or so. Its subsequent rise in popularity is probably thanks to Node (which uses ASI style), and a small group of ASI developers whose code suddenly got more visible once npm came along.

But as a practical matter, the rules on ASI have been the same since forever, and the rules are that they're nearly always optional. The only realistic case where omitting them causes issues is when you start a line of code with a parenthesis or a square bracket. Back when ASI first got popular that was the one big gotcha, but nowadays thanks to linters even that's not an issue.

What you may be remembering is, some years back there were some cases where certain JS tools didn't support ASI. Famously, there was a thing where a popular minimizer (JSMin) broke ASI code and Crockford didn't want to fix it because he didn't like ASI style (he later relented). But I've never heard of an actual JS engine not supporting ASI correctly.
> Extroverts seem to me to live for the interaction, not for the content of the interaction. To me this is the essence of small talk - what is said isn't the point; it's the fact that words are being exchanged that gets and keeps the juices flowing.

This is also true from my observation as well. I would go a step further and say there doesn't even need to be an exchange as some extroverts simply like to have words come from their mouth without regard to what is said in reply to those words (which is what you are saying but put a more exact way). To be clear this doesn't mean 'all' nothing is 'all'. But the pattern is what I have observed for sure.

> extroverts understand introverts in any deep sense. They tend to see us as lacking something vital (this constant social exchange of what is often mostly meaningless information). I

Again I agree. It seems to be accepted that the right way to be is to be social and to interact and if you don't do that you are 'off' in some way. ie 'Not normal'.

> Introverts do understand extroverts though - we know the interactions are feeding a need in them not unlike the need for a fix of a someone addicted to an addictive, although not enormously harmful, drug.

The reason I would say that introverts understand is because they are taking the time to observe and think and not so much what they will say in the interaction.

To illustrate the point take the experience of Dan Ariely:

https://www.thecut.com/2015/07/terrible-accident-led-to-dan-...

"He spent the next three years in and out of hospitals and surgeries, and,
he writes, “since I had little else to do and badly needed distraction,
I began to notice and record things.” "

If you are talking you are less likely to notice than if you are not talking. (I am sure others can bring up apocryphal examples of the same point that I am making).
I have to think real estate investments, employment laws, and other factors beyond what company leadership states openly must be involved. The employee objections here are written out clearly, but the policies from big companies that require more than 50% of time in the office seem like such a tragic compromise that I can't believe they've been fully explained.

The longer companies waffle on these policies the more likely it is they will hamper recruitment and face attrition to companies with more consistent policies.

In-office is much less effective when your team is distributed across multiple sites/time zones anyway which seems to be the new normal.
Others have mentioned the awesome projectile, but I think it should be said that Emacs now has built in project.el which has come in leaps and bounds (though probably still lacks some projectile features).

I use project.el alongside consult[1] which has many convenient wrapper functions over built-in ones, like an enhanced `switch-to-buffer` with project support. I am actually using an even tighter integration called consult-project-extra[2].

The most advanced and overkill solution would probably be to use bufler.el[3] which basically allows you to define your custom logic for buffer grouping.

[1] https://github.com/minad/consult

[2] https://github.com/Qkessler/consult-project-extra

[3] https://github.com/alphapapa/bufler.el
Good point. I think the real value of this story is not that this data is readily available, but that the government is also consuming it - which most people (rightly!) have a problem with. If that's the wake up call it takes to make people pay attention to just how bad "surveillance capitalism" is, then I'm all for it.
Escaping the House Elf Management Trap
I think Rust kinda has a marketing problem: the myth that "Writing in Safe Rust automatically makes your code memory-safe". It doesn't (well, it does most of the time but it isn't guaranteed), but it rather defers the responsibility to other low-level system programmers writing Unsafe code behind the scenes. And oh boy they have a fuckton of responsibility... Stacked Borrows along with various sanitizers can help when writing unsafe code, but it isn't perfect. I highly recommend anyone trying out Rust for the safety guarantees to take a look at the Rustonomicon (https://doc.rust-lang.org/nomicon/), which debunks a lot of the misconceptions around safe/unsafe Rust.

In an ideal la-la land world, there exists an abstract interpreter that can consume safe Rust code and does not enforce any contracts upon the programmer (and hence will never have any undefined behavior). However, real world hardware definitely has contracts which developers have to obey (manually! because of the constraints of actual semiconductor physics! no compiler hand-holding here!). And on top of that all major OSes (Windows, MacOS, Linux) are written in C (so you need unsafe FFI to interact with the OS).
The UFO briefings on Capitol Hill have begun. Lawmakers aren’t impressed.
I'll look into the why a group believes memories are associated with individual neurons as my personal intuition (edit: and this article as well) tells me the opposite.

For example, if I try to remember the name of an actor, I can have hints from my brain telling me "their name starts with an _m_" and "it's a man who played in a movie from the 90's", etc.
A memory feels like it cannot be isolated, it always feels like a composition of different elements that, when put together, describe one thing, or many. The more elements (in that case maybe single neurons, or very small group of neurons) are activated the clearer the memory. A Venn diagram of sort where the overlap gets smaller and smaller. This would explain the "this makes me think of…" process, since a certain number of these elements from one memory will overlap with the elements of another one.

This is completely personal and completely unscientific. And maybe this is neuroscience 101… In that case sorry for stating the obvious.
My team is 1/2 in person and 1/2 remote and it works fine. We don't have the "way way more visibility" problem. I think this is at least partly because my director is remote, and at least one link in the chain of VPs above him is remote as well.
So let's say I implement some job scheduling system like you suggested: One job actor instance per job and one scheduler actor instance to create new job actor instances. The job can be in one of many lifecycle states like started, in progress, etc. Unfortunately, since this is a distributed system with faults there can be network partitions, crashes and such at any moment, so every time the job actor changes state it has to write it down in some highly available database so it can be restarted if it crashes and every time it wants to do anything it has to check that database to see if someone else is already doing it. At that point the actors are basically stateless, so what's the benefit of using actors in contrast to Futures or similar stream-processing frameworks, whose abstraction boundaries are not coupled directly to operational concurrancy concerns and thus much more maintainable when you have more complicated workflows with fan-out/fan-in stages? (Not to mention that Akka Streams provides this API on top of actors with the ability to distribute work across nodes in a network without users having to know anything about the actor model).
https://threadreaderapp.com/thread/1521489115585421314.html
I built a CPU myself out of 74xx logic, but I can't be sure that every input on every chip isn't also connected internally to an integrated computer that stores everything it sees and can transmit it to a van at 20 metres range (easily enough for someone to drive up to my house and retrieve the contents periodically).

The attacker can then reconstruct everything that happened on the CPU and work out what I've been up to. Or, more likely, throw away almost everything and only look at what was printed to the console, because everything interesting goes to the console anyway.

In fact this would be easier-than-average to achieve because the clock speed is low, I don't run the machine for very long or very often, and the density of actual electronics to "free space" on the ICs is very low (more space for shenanigans), and all my schematics are on my github project so even though you don't know which chip is connected to which other, you shouldn't have too much trouble deriving it.

So what now? Do we just give up? Is all computing fundamentally impossible? Or do we accept that nothing is perfect and just get on with it?
It feels just as weird as calling things daylight robbery, i.e. not at all.
Great service and deliverability but pricey if you are in the 125k emails / month bracket. I found Amazon SES to be just as good (or good enough) for just 12% of what postmark asks.
And Disney could have said "no" to any of his ideas at any point. He's become a scapegoat for bitter fans who can't see that Disney didn't know what to do after the first movie.
I'll just throw out there when I started developing all I had was one crappy laptop and headphones and the way I ended up working was by going to the Starbucks down the street getting a hot chocolate and a scone and going to town for hours at a time. Of course that wouldn't work as well for meetings but it was simpler times back then.

Although now I've got an idea to make coffee shops produce more revenue I'm realizing if the CEO of Starbucks is reading this give me a call.
Find a new place to work. Support companies that trust and value their employees.

I personally don't plan to commute to an open office just to use software tools designed for remote work at a desk there instead of my more comfortable, quieter one at home. If I had a private office at work then maybe I'd reconsider.
that's super right. Got first hand unfortunate experience. The simple thing is: please managers don't buy the work-hard-to-compete ethos. It's not because you can take it that others can or should.
Software distribution is a rather critical task in general purpose computing!
I apologize for taking the piss. I do remember the bad old days of IE6 when the open web slightly closed because a lot of sites only worked in Internet Explorer on Windows.

Please, if you have the time, try and fix that prevents it from working in Firefox.
It's feasible to be concerned about both corporate and government surveillance at the same time.