skysight-inc/HackerNews huggingface dataset:
I did a little bit of work on a similar idea but for embedding shell commands in Markdown.

My system is mainly targeted towards readmes and other documentation and the way that it works is as follows:

1. My program reads in a markdown file.

2. It finds fenced code blocks in the file, that have info strings corresponding to a shell scripting language like bash or zsh. For example

```zsh
grep foo bar.txt | sort -u
```

3. Then it looks at each of those fenced code blocks and checks if they are immediately followed by another fenced code block but where the info string is that of plain text. For example

```text
foo
foobar
```

When you author the document you insert empty fenced code blocks like

```text

```

4. For each shell script fenced code block that is followed by a plain text fenced code block, the commands in the shell script fenced code block are executed and the output is captured.

5. The captured output of each such shell script fenced code block is inserted into the corresponding plain text fenced code block that follows it.

6. Any fenced code block that is not immediately followed by a plain text fenced code block is ignored and not executed.

All together this allows for, among other possibilities:

- Updating outputs of sample commands in documentation all in one go.

- IPython Notebook style documents for shell scripts, except not interactive.

- Including commands that you want to inform the user about but which you explicitly don’t want to actually automatically execute.

I have a simple version of it for my own use that I put together a while back, and I started making a version of it that will eventually be usable by anyone. I will probably try and do a Show HN post about it when it is ready for others to use. Currently, completing the version that will be usable by anyone is on the back burner while I am working on some other things.

In my program, each block of code is run in an independent shell. So if you define a variable in one code block then it is available throughout that same code block but does not “transfer” to other code blocks. This is by design.

Command blocks are executed sequentially so that one can do operations that make changes to the file system in different blocks and still have the outcome be as excepted.

For example, you might be writing about generating and optimising png files, and your document might contain something like

First let's generate a 128x128 solid grey PNG and look at the size of the file.

```zsh
convert -size 100x100 xc:grey image1.png
ls -al image1.png
```

```text

```

The resulting file is quite small already.

But we can shave off a few bytes using a PNG optimizer.

```zsh
optipng image1.png
```

```text

```

And that saves us about 10% in file size in this case.

And for me this is the way that seems natural for the use case that what my program is doing. That the code blocks share operating system state and file system state, but not variables.
Counterpoint: life in communist countries is not known for being "not miserable".
It's definitely not doing "nothing". The vaccines are reliably reducing the severity of infection as you pointed out, and also reducing the duration where someone infected will infect others, thus reducing R value, thus applying significant friction to the spread.

It's not the panacea we might have expected, but I think we all misunderstood vaccines from the get-go.
pay.game
I'm not cynical, but I kind of gave up on people who don't behave on the internet or are blatantly stupid. Sometimes this feels like I gave up on the internet as a whole, but I try to accept that it won't change anything whether I care or not. Things will go their way no matter if I fight it or not. So I try to ignore it. But what I want to do, is, I want to upvote more. I want to encourage people to be open with their thoughts and knowledge and create output that I think benefits more people and puts us on the right direction.

Long story short: I try to focus on what has value and encourage that behavior with upvotes and further comments.

PS: What's the required karma to downvote? I'm currently not in the position to be able to downvote anyway ^^

Edit:
(1) "I'm not cynical, but ..." Well, not a good start... I try not to be, maybe I am. But I don't want to be.
(2) Karma required to downvote is 500 according to another commenter
What we didn't hear about is how Boeing is going to change its processes to avoid repeating this nightmare scenario. Because, sure, they fixed the 737Max AFTER hundreds of people died and every airline was forced to ground their airplanes. Who can trust them when they come up with another plane? I, for one, don't.
I want to second this. With quick compile times, fat binaries and first class support for crosd compiling, go is suitable for pretty much everything python would be used for. My only use cases for python are as a replacement to bash for shell scripting.
If you don't trust statistics you have nothing left to trust in, doesn't look like a smart move.
Wow, this looks really promising! Thanks for doing this.

My family back home is hooked on Google Home but sister agreed to switch off for the kids - but her requirement is to be able to control Spotify via voice.

Given I set aside enough of my time to help them out and figure out appropriate hardware, do you think it's worth a shot with HI?
I work on kernel and network performance on FreeBSD. For me the issue with QUIC is that we loose a few decades of optimizations in software and hardware. Eg, we loose TCP TSO and LRO (which reduce trips through the network stack, and thus per-byte overhead costs), and we loose inline crypto offload (which offloads the CPU and cuts memory bandwidth in half). So this makes QUIC roughly 3-4x as expensive in terms of CPU and memory bandwidth as opposed to TLS over TCP.
James Webb launch postponed until Dec. 24th at the earliest
It's not a new idea, but the implications if it goes wrong are severe.
Imagine it mutates (it happens, especially if it's super infectious and thus being exposed to MANY environments and gets to live millions of years per day (time * infected humans)).
Imagine it works differently in a small percentage of people, it's a lot harder to control when it's distributing itself.. With vaccines, at least, administration can be stopped or paused, if cause for concern arose.
James Webb: A $10bn machine in search of the end of darkness
What’s remarkable is that MCAS functioned so well that not a single pilot had noticed it prior to Lion Air.
> If we don't think about this

Actually, in this case "we" means Google and a few other big companies whose aims are not the same as ours - they are the ones in charge. Sure, at times it happens that our interests are somewhat aligned (like page load times) but only as far as it serves them. For Google, a page without their code like ads/analytics is pretty much useless; for us, it's more useful because it doesn't track us and loads faster.

So yes, while they continue doing some work in that respect, I expect it will actually go worse with time as they are focused on average consumer bandwidth in the USA. Once G5 is well entrenched and broadband/fiber gets even faster, we can expect even more bloat on websites and there is not much "we" (=users and developers) can actually do about it.
String is a pointer/slice type under the hood, even if you don't see the asterisk. So when you are passing v, you are passing a reference to a slice which gets updated by the loop. Since the goroutines can run in parallel, you print whatever v is pointing to at the time.

C++ lambdas do the same thing if you pass a pointer.

Python would do the same thing if you had a mutable non-threadsafe objects passed to threads. Eg if you iterate over a list of dicts, and modify the dicts, you'll get the same effect.

So then the question becomes, why does v get re-used, instead of assigning a new pointer each time? Dunno, probably performance. I could see the latter generating a lot of garbage, which can be totally avoided if you don't pass mutable references to goroutines.

What go really lacks IMHO is some kind of const modifier for these kind of references. Maybe it does, all I remember are const scalars.
> The price you pay for such little actual utility isn't worth it.

It is for us. The use case that sold us is my partner cooks a lot and often needs to add reminders or update a shopping list, which is difficult with both hands dripping with raw chicken juice or dough or whatever. They were for sale a while ago for $30 a device and they are decent speakers to boot, better even than a $1k phone.
What do you think of the science subreddits? r/science for starters. I first came to HN from reddit because I thought the technical discussions here were superior but now, even deep “tech” (i.e computers) discussions may find a better home back in reddit.
When black men (some of the earliest investors in the US project) were 100% employed they were poorer than ever due to racism. We can't seriously act like investment decisions during our 'inflationary present' can overcome the ~2 trillion hours of labor the US and its white citizens stole from black citizens, roughly $40 trillion of wealth.

Reparations is the only solution.
That same line of argument could work for socialism/communism. What country that doesn't use the free trade paradigm for their economy isn't some authoritarian nightmare of poverty and despair? Are they just bad actors using the system wrong, or is it a system that always ends that way?
2 jabs should be fine too. Especially if you had a huge gap between the two doses.
Popular music changes every 5 or so years, because freshmen entering high school want their own identity that's distinct from the seniors who just graduated. This is why they can reject the music wave that came just before, yet also embrace nostalgia for the prior wave that came before that. That's fine, because the previous wave of kids (from which we want a separate identity) weren't into that wave.

This teenage dynamic carries over into adulthood. Academia is a bunch of young adults chasing tenure, by publishing papers arguing that the existing batch of tenured professors are washed up and got it all wrong. And also "rediscovering" the older research that was discarded by the previous generation.

Software development is a bunch of a junior devs working on bug tickets. Frustrated by the tech debt they inherited, and convinced that tech debt comes from the tech rather from the organization. It's just that in comparison to academia, technology has the generational lifespan of fruit flies. So we spin through the cycle a lot faster than other walks of life.
Alternatively you can remove the laptop battery and use it with just the charging cable attached to power the device. The laptop will automatically shut off when the power cable is disconnected. Then PAM Duress [0] can be used for the xkcd538 [1] situation.

[0] https://news.ycombinator.com/item?id=28267975

[1] https://xkcd.com/538
Other sites refer to those sorts of threads -- threads for general discussion of a topic or question rather than of a specific article or detail -- as "generals", e.g. "FLOSS Dev Compensation General", "Log4j Vuln General", etc.

Long-running threads are better suited to discussion formats with strict time ordering. I'm not sure how a vote-ordered hierarchical comments section could keep up a clean presentation of new developments in the discussion. Linking between threads doesn't look like a practical solution to me; I expect we'd still see the same exchanges rehashed in each thread.
Data stored in the cloud should be considered public (at this time), but not the data on your device.
Indeed. The “banking should be public infrastructure” never make the connection with their comments about Guantanamo and the TSA.

“We don’t need a warrant to see your banking transactions since the government itself provides the service”.
I myself am one of these people. But even if Ruby worked anywhere and I could share all my code, I would still prefer TypeScript because of its support for typed JSX and excellent typing system overall. The IDE can help me in most cases, while it stays silent a lot with Ruby. I just don't see what more Ruby offers - and I'm saying that as someone who really likes OOP and really wanted to like Ruby.
For some who listened to their government or the WHO it now is.

For the rest of us it was since mid 2020 when real news sites presented compelling evidence.
People don't directly consume very much energy; most of our energy footprint is derived from the processes to manufacture the things we consume. Much of that has been outsourced in the last several decades.

Moreover, looking at overall energy isn't particularly informative without also analyzing energy costs--according to https://www.statista.com/statistics/183700/us-average-retail..., the energy costs have increased 60% in the last 20 years which would obviously suppress consumption.

We're talking about the opposite--how does our energy use change if prices fall dramatically. Are we really going to replace fossil fuels or do we just find other uses for this new electricity? For one, we're going to be electrifying other applications--all of these new electric cars are going to place new demand on the electrical grid (previously they were energized by gasoline and as such didn't burden the grid). But beyond that, are we going to actually use any excess energy capacity well, or are our applications just going to get less efficient (why should a factory invest in a more efficient machine if energy prices drop precipitously? economics favor the less efficient solution in the same way the economics of plummeting data storage and transfer prices favor bulky electron apps over streamlined native apps).
You're correct about being able to match serial numbers, but they are still nowhere near being in the same league.

A stranger across the world can't track your physical currency in real time. Whenever serial numbers are checked (if it ever is), the tracker just knows that bill was at that spot at that time, they don't know how many times it was exchanged or where it was since it was last tracked.

With BTC, anyone can track it in real time, anywhere. The same cannot be said about physical currency.

I suppose it's not a stretch to imagine banks have a machine that scans serial numbers (eg to catch DB Cooper's cash), but I've never heard of any evidence of such machines.
Not sure what to tell you. The link worked fine for me and I don't have a login. As the sibling said, the audited financial statements take a while to complete. But budgets and financial statements and reconciliations between them are public, have to be by law, and you're also free to sit in on the legislative sessions when the budgets are approved. None of this is "easy" but I don't know what people honestly expect. They can't just open up the agency ERPs to anyone without an account, for obvious reasons.

I see this entire comment didn't go over well. People love to shit on governments. I used to be a budget officer in the US Army, in charge of the 1st Cav's efforst to digitize all records at the time the DoD was attempting to produce the first GAAP-compliant auditable financial statements ever in its history. We were digging out paper receipts from filing cabinets in rooms people had forgotten existed to upload into the SAP ERP, an extremely time-intensive and error-prone process, at the same time the sequester was going on and all the civilian staff had been furloughed, and half the headquarters was deployed to Afghanistan in the middle of this.

This is actually hard. Governments are held to much higher transparency and accountability standards than private companies, all while constantly having their own budgets cut and staff reduced, with no investment in automation or interoperability between disparate information systems and sources of truth.

People just expect this to be magic and free for some reason.
"A stop job is running."
Wouldn't it make sense to remove the battery on your laptop entirely? With a modified magsafe-like power cord any attempt to grab the machine hard-kills the system and RAM begins degrading immediately. Epoxy over the screw terminals would also delay an attacker long enough to prevent freezing the RAM with compressed air to try and dump RAM via an exploit kit.
Slack message on fast repeat is giving me PTS(D).
The only problem is this is sort of obvious from a forensics perspective. Person is using truecrypt, they boot it up for you, and the partition is only half the size it should be.
The reason is that a) if it doesn't look good, most people will not take it seriously and b) you must have ads and tracking of user activity.

What I really don't get is why bare html looks so awfully today and you have to add tons of js and css to get something acceptable.
Other than the fact that this is reactionary garbage, why is it on this site?
Typing is almost a no-loss addition though. If your function takes an integer argument and someone might pass it a string, that is a bug. It is quite hard to argue that a typing mechanism won't improve code quality, and it is very lopsided in the amount of time it takes to type a function vs. debug something that would have been caught by a type system.

There are edge cases that can be argued all day, but if some large codebase is going to be maintained long term it is difficult for me to see how types could be a handicap. Even if a coder doesn't really engage with the type system "properly", as little as capturing information that was already obvious anyway will reduce the bug count.

There are good reasons to expect typed languages to do well.
There are real, hard problems worth discussing at the root of all this. Extending lists of taboo words, however, is really easy. Judging if somebody uttered a taboo word is easy. Let's just all focus on the taboo words and pretend there is nothing complicated to deal with.
Anyone interested in HTTP 3 that likes even-handed articles, Robin Marx has an excellent series on Smashing Magazine: https://www.smashingmagazine.com/author/robin-marx/

The second article is about its performance.
I imagine they mean this. https://www.cnet.com/tech/services-and-software/samsungs-war...
The worst is users with the ability to flag content.

I have dead comments turned on and see a lot of well-made thought provoking comments that that are flagged because they are contrary to the popular narrative.

On the other hand there are a lot of bad comments that deserve to be flagged so it's a double-edged sword.
It appears like a good explanation. But other commenters have pointed out how it lacks precision. Name dropping CSS modules, React query and other technologies is marketing, not research.

By comparison, this article properly analyzes an actual industry trend, not generalizing one developers experience: https://martinfowler.com/articles/micro-frontends.html

I’m not a believer in micro-frontends but the quality and intent Marin fowler’s of writing is actually respectable.
That’s why it needs to be destructive. You can’t beat access to something out of someone if it has been deleted.
Securing AWS Secrets Using HashiCorp Vault with Terraform
A month of effort to avoid a day of downtime, and six months of unemployment.

I worked in a business where if the website went down we missed £26m revenue. This is not a particularly big business in the modern sense. However, one MD had a screwed up migration that didn't have a good roll-back plan. There was a missed day of revenue, and he - and several others in his top team - left the business within a calendar month.

This kind of thing colours my view on prod risk.
In Belgium, the first jab in June I was waiting in a tent in tent with others, tent was mostly opened. Second jab in July I was waiting in a closed store space, sitting on a chair, within 1.5 meters of each other.

I will most likely get the third jab in mid-january according to schedule so I am pretty sure I'll be standing outside for a bit (if I can) this time :).
My parents installed that in 1988. The technology has existed for years. The power company charged half price for electric and gave them a second water heater so that they could heat the water at night (electric company controlled), and when power demand was high the air conditioner ran for 15 minutes, off for 10. (this mostly meant we kept the AC on all day, it wouldn't cool the house off when we got home but would keep it cool all day and cost less than setback thermostats). Refrigerators were not on the plan, but they don't draw near as much power.
You didn’t get the memo that this was a lifetime subscription service?
I seem to have that issue with the dentist while they’re injecting into the gums or whatever. But shots in the arm don’t bother me at all.

Something about the inability to see whats going on, I just imagine the dentist panicking but trying not to let me know while the spit vacuum is draining my blood.
My Own Addition:

14. Those who code for a living make good money.

I have a lot of friends who went into various fields, and it seems relative to the number of buttons we press daily, anyone who works on software makes great money. We didn't spend a ton of $ to go to medical school and 3 years of residency. We didn't go to law school and take the bar. Most of us went to 4 years, or less, of school, and here we are making great money by utilizing the greatest tool of all time: the computer.

It's uncomfortable because many of us didn't understand this going in. We liked computers for a long time, we had a penchant for working with them, and it turned out that made us great money. Meanwhile, our friends who are teachers, firefighters, child-care workers, etc. are doing tough work daily for less pay, perhaps simply because they didn't use computers much or didn't like them. And yet, their jobs are ESSENTIAL and we need people to do them even though they're grueling and underpaid.
Languages that allow the creation of such DSLs do, in the end, seem to be gradually declining in popularity. This is probably because it is difficult to add static typing to a language that flexible. (Even in JavaScript this has proven difficult, as shown by the fact that TypeScript is known to be unsound.)
SCTP runs over UDP too. The main reason for not picking it is likely the TLS handshake optimizations they wanted.
> who would spend 1.500 euros (in Europe) for a laptop that has a limit of 16gb of RAM?

Let's say you use a laptop for 6 hours a day, five days a week, 48 weeks a year, and that it lasts for 3 years. That's 4,320 hours of usage. For many people, it's worth paying 35 cents per hour to use a machine that's even just a little bit better than one that costs half that. I'm writing this on a high-end Macbook Pro that's 8 years old. It was very expensive when I bought it, but the "cost per hour" has actually been quite low. The benefit of a better experience during the entire duration of usage is well worth the added cost, in my experience.