skysight-inc/HackerNews huggingface dataset:
Did Functional Programming Get It Wrong (Part 2) – Minecraft-Style Crafting
I am still waiting that he gives 99% of his wealth for a good cause, was that just some AI-hiccup?
"These are the new leads. These are the Glengarry leads. And to you they're gold, and you don't get them."
yeah, I just always assumed it was showing off the 256-color capabilities of VGA for that version—the original CGA art is more cartoony-looking.
maybe you can find some useful information here :

https://www.reddit.com/r/lisp/comments/vmpbcd/thinlisp_lisp_...
I wonder,

Where there any crypto investment Funds that invested in actual companies (aka not coins or derivates)?
Some of the Cutest Dogs at Amazon
Assuming they don’t just do machine translation.
SEEKING WORK

Location: India
Remote: Yes
Willing to relocate: Yes
Résumé: gnanesh.me/resume.pdf
Email: gnaneshkunal (at) outlook.com
Github: https://github.com/GnaneshKunal
LinkedIn: https://www.linkedin.com/in/gnanesh-kunal/
Technologies: Python, Golang, Typescript, Rust, React, Redis, Docker, Kubernetes, CI/CD, Postgres, Cypher Query, Distributed Systems, Cloud computing, OpenTelemetry, Google Cloud, Reverse Engineering, Distributed Tracing

I have been doing Golang, TypeScript and Python professionally, mostly targeting Backend development. I have led JavaScript to Typescript migration of frontend and took complete responsibility to add multiple enterprise backend modules with test driven approach. Furthermore, I tend to be a T-shaped person with the core in full-stack/backend and consistently learning leadership skills. I understand database internals and actively contribute to Redis ecosystem. Properly skilled with distributed technologies and cloud native patterns. Currently working for a fintech company. I have multiple independent contractor experience spanning from desktop & web application development to reverse engineering mobile applications. I also contribute to OSS during my free time.
Please mention HN while connecting with me.
Thanks for mentioning these.

Is design + doc your primary use case?
I doubt that fog carries calcium - though dust will surely be in the air.
I didn't see him on TV, I read an article on a newspaper about the issue, I dont' think that there was anyone playing martyr, nor any intention for indentured labor or similar, it was - as I read it at the time - simply a rant about the scarcity of qualified drivers and the difficulties in hiring new workers (unqualified) and assist them in getting the license, as doing that would become a too large investment for the firm, and asked (this is actually italian entrpreneurship) for some form of assistance by the state.

At least in the interview he stated that the people would be paid the national contract wage, roughly 3,000 Euro/month net, which is "market salary".

Here is the online article (the one on the actual newspaper was longer and more detailed AFAICR):

https://www.corriere.it/economia/lavoro/21_agosto_11/cerco-6...

(not too bad in Google translate).
All the stuff that uses GPGPU computation heavily.

- Weather prediction.

- Other aerodynamic and hydrodynamic modeling, used in a lot of industry.

- Image recognition.

- Voice recognition / captioning.

- Machine translation.

- I suppose also stuff like large-scale mechanical modeling, protein folding models, etc.
Can you share how your pipeline looks like? GPT-3, BERT, GloVe...?
>Which package do you use for the linear algebra calculation?

He doesn't. https://github.com/codemix/deprank/blob/main/src/index.ts#L1...
Tracking Everything I Wore For 1 Year
No picture of the crab or the whiskey in the article, just some guy pulling up a huge metal cage into his boat. And why is this on Hacker News anyways?
> All this panic about tech layoffs seems a little premature given we haven’t even begun to see the impact of rates hikes on quarterly earnings yet. Many companies still have open recs and budgets to keep hiring.

I think that's the main point. Tech is going nowhere, it's crucial for the future for most countries around the globe.
Sometimes the criticism is delivered directly to you, in a community you care about.

It's one thing to know that someone on the internet dislikes you. It's another to see someone do it within earshot at your favourite pub.

People on the internet make the sort of quips you'd never make within slapping distance of the subject. They do it where the subject hangs out.
Democracy is also two wolves and a sheep voting on what's for dinner. Remember that Hitler was democratically elected and the head of a coalition government, before taking indefinite emergency powers.

Protecting rights is more a consequence of the rule of law, and equality under the law.
Have you tried Tailscale? I have and our company is going to migrate in the next year or so because it does a LOT of stuff better.

As for your rule limiting submissions to the front page to only one every month. Who’s gonna moderate that? Are blog posts about the product also prohibited? Cause that is how I learned about Tailscale in the first place.

My point being, no I wouldn’t want a rule to moderate something like this. Because I come to hackernews to learn about these types of stuff.

Learn to ignore stuff in live you don’t enjoy.
Flask supports async, see https://flask.palletsprojects.com/en/2.1.x/async-await/.

Also see Quart https://github.com/pgjones/quart (which is Flask re-implemented with async-await) and Quart-Schema, https://github.com/pgjones/quart-schema for swagger docs.
Some discussion from yesterday: https://news.ycombinator.com/item?id=31939871
For a large interactive single page application you probably still want to use React/Vue or similar.

But for a small, simpler app, maybe one you are working on alone, only having a “backend” is appealing.

I’ve been using Alpine on a project recently and removing the overhead of a frontend to manage has made progress faster.
You're describing a pension.

I'm gathering from the comments that this isn't a globally recognised term, but it's like a flat (or inflation-linked) post-retirement salary based on how much you've paid into it over the years. If you don't get to a pensionable age, you get nothing. Longer you live after that threshold, the more you get paid.
Oh it was workable. Until it wasn't. I specifically remember extricating a high throughput web service from pandas. Having to scale made that stuff harder. If it was some app that a few thousand people were using, no problem.
Ive seen some posts/tweets that There are cards exiting the crypto market where failed ram chips on them have just been yanked off the board, as crypto just needs cores not lots of vram, i wouldn't trust it unless very, very cheap to lower my risk.
What are the strengths and weaknesses of Darwin?
JamCoders: Algorithms/CS summer course for high schoolers in Jamaica
It is also easier to manage for Flask - it is very mature and we fixed most of the issues present in FastAPI many years ago.
Why do you care what other people do? Just focus on yourself.
Even if we got emissions to zero tomorrow we’d still be in serious trouble.
We need carbon capture.
Emission reduction just reduces our rate of acceleration towards destruction.
We need to hit the brakes.
It mentions that the area has strong winds, and the nets are a bit pricey to replace.
Why...? The reason it's problematic in the present is the over time reduction in the effectiveness of antibiotics. Is the assumption here that the same will be true of CRISPR drugs?
Interesting article, which gives some good idea how to structure concurrent programs with less shooting at your feet :). A bit long winded until it comes to the actual core concept being presented: spawn concurrent routines within a block which doesn't exit until the last routine has exited.
This is a good concept an can make a lot of code clearer. It prevents some data races, as you can reason that after the block no concurrent operations are still ongoing, but of course it could make the block lock up by itself, if one of the routines doesn't finish.
This is certainly an interesting concept I might try out myself more specifically. It is also important to know, especially as the "go" statement of the language Go is put into the headline, that this very language already supports nursery-like structures, just doens't have the syntax sugar the python extension of the author has.

It is called a wait group. See for an example here: https://gobyexample.com/waitgroups

So, except for the syntactic sugar around it, the nurseries compare to creating a wait group in a block, spawn goroutines which each call Done() on the wait group on exit and at the end of the block call Wait() to errect the same boundary, nurseries do. Of course you can also pass the waitgroup object to any goroutine created inside goroutines. This is a very common pattern in Go, but indeed, it probably should be presented more clearly and up front in tutorials about goroutines.

So for that, I will keep the article around, it shows the concept nicely - perhaps I might do a pure "go" version of it, which then shows the go implementation of nurseries. Might be nice to add to the original article, that not only the presented python library is a solution, but also that there is a native go way of achieving that, as the article uses "go" as the negative example :p
The example at the top of the article isn't very good. It is not clear to me that the manager didn't do the right thing. So the issue took 3-4 weeks to get solved.

"Everyone, including that manager, operated as though they were collaboratively discussing the issue."

That doesn't sound so bad. How do we know that the manager didn't "oversee a timely resolution"? Not everything needs to be solved yesterday. Maybe allowing everyone to collaborate on the issue and let it stew for a bit lead to the best outcome.

Speed != productivity != quality.
Arguably, we should. Henry George claimed that a more just society could be achieved with a near-100% land-value tax. If your house sat on valuable land, you would very quickly get pushed out by being unable to pay the land-value tax. Georgists (of which I am one) believe this results in a society that is better overall than the one we live in today.
I feel the same. I tried playing around with server-side JSX in Deno and HTMX. JSX seems like a good solution for backend components, esp. since it's more suitable for reusable smart components with logic or data fetching and not just "dumb" templates.

https://github.com/dsego/ssr-playground/
When I run into people like you, I'm amazed this place even lasted a year.
From Design to HUGO video tutorial
Many automotive MCUs have complexe timer coprocessors integrated for hard real time I/O purpose. Examples are GTM, eTPU and N2HET that I know about. Does the PIO work in the same way?
> it is still profitable

> I do not pay for power

I guess you don't run your own solar farm so I assume someone else is paying that for you without knowing.
How do you evaluate your own beliefs and any claim you hear? Sorry, but this sounds like a roundabout way of calling your political "opponents" dumb for believing the things they do.
If you have to take a job you don't like to be able to afford the house, be aware that nothing changes once you own the house. Most likely you'll still need the job to afford the running costs of the house.

There's no "I'm free once I'm a home owner" thing.
Library bookshelves are cool as well. Overbuilt. Insanely robust. Those bookends don't move, the rest of the earth does.
This was simply an explicit (although obviously not explicit enough to the people taken advantage of) scam from the start. There was no cryptocoin. No blockchain. There was just giving money to her and her associates.
What about gaming? People have been waiting to be able to buy affordable GPUs for a while now.
Because the article isn't about go. It's about structured concurrency. Goroutines were just a convenient placeholder for the current unstructured concurrency primitives most languages have (and it fit their goto/go narrative)
Agreed, Alpine and the like work great when building your app in Laravel.
Nothing lasts forever, but very little changes overnight either. If you're paying attention, you can watch the arc of growth and decay in many places.
And then people burn the methane in their stove, thus producing CO2.
> The only safe thing to do is boycott information

You do realize how it sounds when you say things like this, right? You're not going to convince anyone to your way of thinking by describing the way you respond to challenging ideas as "boycott the bad information."
> back-end juggling this stuff just to make these guys happy?

I don't see this design pattern as forcing a particular back-end framework?

It's merely shifting the frontend<-->backend contract from JSON to HTML.

Some backend engineers arguably would prefer HTML. Especially if their backends weren't Node. Backends were originally C servers that sent a string of HTML back.
I think backend engineers are fully capable of "juggling" with this new/old paradigm.
How the US Air Force Ditched the Average and Saved Lives
See also AddisCoder [1] (in Ethiopia), which this program is heavily influenced by. Unfortunately, this has been on hiatus due to covid.

They have an incredible team leading it [2]. In terms of open-access education, the one I've followed most closely is Jelani Nelson, of Harvard Advanced Algorithms etc. YouTube fame [3, 4].

[1]: https://www.addiscoder.com/

[2]: https://jamcoders.org.jm/#team

[3]: https://www.youtube.com/watch?v=0JUN9aDxVmI

[4]: https://www.youtube.com/watch?v=s9xSfIw83tk
Wow, this is an incredible article. He nails every single point.

I have a strong feeling that coal burning is about to increase around the world because of the attitudes of a lot of detached environmentalist who don't want to think in logistics and tradeoffs, only what feels good to them.

It seems like Europe is set up up a humanitarian crisis on the same front this winter.
The issue is constant running also has thermal cycles, the variance between peaks is just lower, but can be more rapid. (Spikes from particular instructions being more power hungry).

Also in this case we have mechanical components under constant usage (fans), and the effects of long term heat on the thermal compound between the die and cooler plates to consider.
I don't understand what's the scam in this. You buy BTC because you either seek to profit from it, or you believe in the core philosophy behind it. Both of these are your own decisions.

A scam would be you buying a phone from Amazon and getting a brick. BTC is exactly what it describes, nothing more, nothing less.

If you got greedy enough to dump your BTC onto a centralized service for 3% yield, that's on you. As is the decision to buy BTC.
Off-topic: I've read the name as if it were "de-prank".
Adding React is a big decision.

You’re adding a lot of complexity to your project which may be unnecessary if you’re app is a simple website with a few interactive elements.
tlc essentially uses brute-forcing, apalache uses SMT solvers.

tlc still has some advantages over apalache in some conditions, but actually I've never even used apalache with my models (I'm still in the practice phase, though).
About your questions:

No i haven't tried it since it's not something I need. However my point was not about Tailscale being a good or bad product. My point was about the amount of a product related articles in the front page of HN.

Let's suppose I had a product in the same space as Tailscale. How was I supposed to get any customers if everybody in HN knew about Tailscale?

About the rule: I think once a month is enough; the article would get traction and you d still see it and learn about it. The duration is not really important, it could be 15 days is a month is too long. But definitely not every 3 days like it is now!

Finally, the moderators would do the moderation. Users would flag frequent Tailscale articles and the moderators would demote them.
According to industrial producers of atrapanieblas, FogCollectors, at https://www.aqualonis.com/ , they «requir[e] no maintenance».

The maintenance mentioned may be a more basic, procedural one than a structural one. They seem to be relatively simple.

«When the nets wear out, the villagers will have to replace them at a cost of 100,000 pesos each» - that's ~100€|USD.

I am not sure where you read that «biggest implementation hurdle», if it was the sentence «The question is not whether the fog collectors work but who’s going to provide and maintain them», I do not read that so strongly.
Dinesh D'Souza is a scam artist. Do you also still believe that the MyPillow guy is going to release that evidence of voter fraud he's been holding onto for two years? You've been conned.
That's not usually how technology development works - usually it's tiny steps in adjacent problems/products which suddenly coalesce into a new product, rather than working for 20 years solidly towards a single product.

Take VR as an example - A company that worked on VR since the 80's wouldn't have been unsuccessful, but the reason that the Quest 2 exists today is because of the smartphone, and the smartphone was built on the basis of large flash memory, mobile phones and laptops.

Or AirPods, which built on the foundation of over-ear bluetooth headphones and wired earbuds. Bluetooth over-ear headphones obviously built on the foundation of wired over-ear headphones.

NB: All of the technologies these built on the shoulders on were stable technologies which were generally received well in the market allowing continued investment in R&D. The closest thing this builds on is Google Glass or Magic Leap, both of which have been a commercial failure and are both a long way off a polished consumer product - and neither of those solve a lot of the technology issues here.
4000 series is also a 500-700+W space heater if the rumours are true... Nvidia taking the Intel playbook of shove more power through it to speed it up, it hasn't sublimated yet..

Between electricity prices, and climate change making summers uncomfortable as it is, that's a no go.
This is going to be hard on highschoolers who have jobs. For many, it will preclude them from working.

And before you say, "Good!", keep in mind that not everyone has the priviledge of an all paid ride from their parents.

I personnally never had any proble getting up early, but I went to bed at a reasonable time. My peers who had trouble in the morning all tended to stay up late.
Resolving to a hostname in n AWS using a tag is eirksome though. MagicDNS on the other hand in Tailscale makes it easier.

FWIW I use both SSM Port Forwarding and Tailscale but Tailscale is easier for both tech and non-tech users IMO.
"We"?

You assuming everyone on hackernews is American again?
Zerotier works at a lower level. This means you can do other protocols than tcp/ip
I think it's weird how so many people seem to think solid state parts or chips can't fail due to lifetime/heat/use. They don't have obviously moving parts like a fan, but that doesn't mean its materials can't degrade.
I used Spin a few years back, so my memory is a bit hazy, but I remember Promela (Spin's modeling language) feeling extremely low-level in comparison. It felt a bit like more limited C with non-deterministic choice stuck in there. TLA is a first-order logic language, and the tooling (while not great by modern language standards) felt more pleasant than Spin.

It could be that you get faster model checking with Spin though, I'm not aware of any comparisons.
I think you missed the point of the article. Its suggesting that goroutine style concurrency should be completely replaced.

Much like if/for etc has replaced goto, structured concurrency can replace goroutines. Note: goto can be used like an if or a for loop. You've just made the argument that goroutines can be used like 'nurseries'. You've essentially argued in favour of goto from the articles perspective

I want to note again that this article is not actually about go. It is the same in most languages with concurrency primitives.

The key takeaway is that having to manually manage waitgroups is room to make mistakes or to introduce spaghetti concurrency, while you might be used to it at this point, it doesn't make it the best system for the future of concurrency
The thing that weirds me out the most with ffmpeg is that they have input and output flipped. Input needs a flag (-i), while output is a flag-less argument.

Every other tool I know has either an output flag (-o) or takes the first argument as input and the second as output.
This is where we will see how desirable Facebook still is as an employer. It used to be at the very top of the hierarchy, but it has become extremely uncool by 1) being defeated by TikTok at its core competency of building addictive apps 2) been dragged in the court of public opinion as an evil empire and 3) losing a large part of its market cap.

In this recessionary environment people won't have AS many choices as before but I still think you will see a ton of regretted attrition as Zuck "turns up the heat."
> Tailscale also provides an authentication layer (ie username/login/passwords)

Unless I'm misunderstanding you, I don't think it does (having to use a a third party to sign in is one of the main reasons I haven't tried it yet). From https://tailscale.com/kb/1013/sso-providers/: "Tailscale never handles authentication itself."
Why not just use JavaScript + HTML?

<img src="my_cat.jpg" alt="My cat" onclick="this.src = 'my_other_cat.jpg'">
A lovely idea and great teaching book to get kids into electronics.

I was hooked at a very early age by curiosity about the glowing valves
in the back of our radio, all intricate coils and plates bathed in
strange light. A sense of wonder paves the way for lasting interest.
I've been doing similar projects (ecommerce apps) with both Django and Flask. I would choose Django over Flask anytime. MUch less fiddling.
Zerotier almost got zero coverage, but it existed long before tailscale.
It’s also not a YC company
JFYI:

https://news.ycombinator.com/item?id=28327893
why dont you use zerotier?
This article [in Spanish] about the "atrapanieblas" seems fairly informative:

https://lacontaminacion.org/atrapanieblas-un-sistema-efectiv...
I am working on creating a hosting server that can cater to landing page+blog+selling digital content with minimal maintenance overhead.

Beta version is ready here https://github.com/newbeelearn/sserver

I am looking for following
- marketing and sales (I need some guidance from experienced marketer who has done this before)
- beta users to try this product and give feedback so that i can improve
- frontend for admin UI (backend api's are ready)

I can help with golang based backends if that is needed by anyone.
> The work got safer and injuries happen significantly less often.

For this kind of statement about lifespan i assume that we remove all accidental deaths since they are just causing noise versus the actual lifespan
I also have the same opinion but I keep it to myself since this is not something I can prove somehow. That's why I don't think it would be proper to accuse them of AstroTurfing.

However the fact that this product is about networking makes me even more suspicious about a very elaborate voting ring.
Black Mirror had an episode covering this very issue called Hang the DJ. (Spoiler alert!) Essentially a giant computer was simulating billions of human-to-human relationships using virtual (but sentient) people to see which would work, and which wouldn't, in order to make a dating app more accurate, before culling them off. I thought it was absolutely terrifying, yet most viewers overlooked the ethical issues of mass simulation of life for trivial purposes and thought it was cute(!) (I should stress that in the episode, the virtual people caught up in this are portrayed as being sentient and aware, they're not just a bundle of numbers and formulas like "people" in a game like Simcity.)