skysight-inc/HackerNews huggingface dataset:
> Is it a better bet to move on and go full Rust, rather than bother with wherever the goggle golang train is headed?

Ecosystem aside, with Rust you'll get far better language design (generics fully integrated with everything (stdlib, consts, all libraries), sane error handling, sane dependency management, no "any" type, editions, and more. More complexity too though.

> Certainly some problems will benefit from the addition of generics, but is it really enough to justify the added complexity?

Coming from languages that have them, it's just hard to take Golang seriously,
where every library either ditches type safety (more runtime errors I wouldn't have with other language), or forces you to copy-paste code just because you need support for some new type (more boilerplate to maintain == more errors).
Or reinvents generics with code generation and aboriginal characters.

Once you start using generics, they really aren't complex.
It's ridiculously easy to vote and with early voting being extended for WEEKS and mail-in voting also an option, there is no excuse other than apathy, ignorance, or laziness. If you can submit a tax return, you can vote.
> Do you think Generics will be an overall win for the Go language, or will they be overused / end up making code harder to read / harder reason about?

Here's my $0.02 from a java background. There will be cases where someone overuses generics. That happen pretty much every time a new language feature lands in any language.

However, my expectation is that like java, you will see Go generics in general practice only come up when dealing with things like collections. Once the community settles and stops trying to use generics as a meta-programming language, they will become pretty boring (which is what you want).

From a readability standpoint, IMO, generics in Java don't really have a negative impact on readability. Sure, you'll get the random `Map<Map<String, Object>, Object>`... but most people see that as the anti-pattern it is.

In short, I'm guessing they'll be a win.
When I was a child about 40 years ago there was a slogan "हम दो, हमारे दो" which translates to "We are a couple, we will have two children". Then in my teens it turned to "हम दो हमारे एक", ie, "We are a couple, we will have one child". It was on TV, in print ads, on the sides of buses, everywhere. There was also a huge move to make contraception easily available to every woman in the country. Then in the 90s TV was privatized and it all disappeared.
You should plan all work when writing software, even if you’re AGILE
I use Go because it compiles quickly, the GC is reasonable, the ecosystem is good enough, and it's not rocket science (Scala/Rust/etc).

While generics moves Go in the direction of rocket science, it feels like this is solving a problem I always have.
Oh yeah! I had forgotten to mention that.

I can't really blame people for thinking that the Linux desktop experience sucks, to be fair. As someone who used it in 2012 and went through the pain of getting an Optimus graphics card working correctly, and dealt with the weird rendering issues of Gnome 3, and had to write a bootup script to disable "tap to click" on my mousepad, it's a reasonable complaint to say that the Linux desktop is unfriendly.

I think a lot of people would genuinely like the 2021 Linux desktop experience if they tried it, but I fear that it will be quite difficult to shake the (well earned) stigma.
> NFT markets don't visibly crash,

That's a really good point. When a meme stock crashes, it crashes down to raw asset value minus transaction costs.

When the raw asset value is less than transaction costs, the price doesn't drop, the liquidity just vanishes, since there is no "negative price" support like there is for assets that are expensive to hold, like oil.
Lol, that's not "just" what your first comment said. You said: "Seems like a sub that's really into respecting oneself outside of the context of a boyfriend, and women unpacking and de-normalizing the toxic behaviors of previous partners." Your original comment is still up there, directly contradicting what you've now pivoted to. You scanned the sub and couldn't find something that it took several other people less than five minutes to track down.
impressive!

Whrereas I (alone) finished two client projects this month (programming) and am starting the third. Help colleagues with their stuff, and am supposed to work on an internal project ( client projects are merely a distraction from the internal project ). I'm also supposed to make a certification ( I'm not sure whether in my free time or not ). I'm paid for 24h a week. And I have bad concience every standup because I didn't manage to finsih more the day before.
I'm definitely not that familiar with Ethereum, my thesis research was on Bitcoin but I have been fairly tuned out since then.

But wouldn't confirmations take, as you said, five minutes on a good day? I see people saying 5-20 minutes typical for Ethereum to reach 30 confirmations. And sure you can accept fewer but 30 seems a pretty widely accepted convention. That's still slower than wire transfers which are functionally instantaneous (in practice of course it takes a minute or so). And right when I looked now the base TX fee is $19.10, which is a few dollars lower than I thought, but I see that it fluctuates by a few dollars pretty quickly so it would depend on the moment. I don't know the Ethereum situation with regards to EIP-1559 in very much depth so if I misunderstand how fees currently work please correct me.

This seems to put Ethereum basically right on par with what my credit union charges for wire transfers. Now $20 is on the lower end for wire transfers on a consumer account (I think $25 is common), but you can also get lower on commercial accounts. It just seems like they're fairly on par with each other from a fee perspective, and Ethereum is at least a few minutes slower.
Great. But the average teenage girl is still more interested in a teenage boy
Apologies for the tone, but the content of my point 100% stands. For what its worth, I have dear friends at multiple FAANGS who I'd die for -- who nonetheless strongly appear to have a wildly overinflated sense of their own cybersec, in a big picture "missing the Black Swans" sort of way -- if the past is any indicator.

Maybe it's not, maybe you guys have drastically improved things. What makes me strongly doubt it is that we still haven't seen substantial liability or other consequences for bad or negligent actors in this space.
The balls you have to say your app is too expensive... THEN ask for help as you try and become and indie developer on same platform!
I understand the "too much Magic" criticism of Rails from novices & intermediate Rails developers, but once you reach a sufficient level of mastery, I think this goes away.

After using Rails every day for 12 years I know pretty much all the ins and outs, and what is "magic" to others is just the robust tooling I love. Just like any tools, they are overwhelming and daunting when you don't know how to use them, but once you become proficient with them, they make your life so much easier. While it might be difficult when the "magic" doesn't do exactly what you want for your edge case, when you have a sufficient level of mastery, it's easy to find a way to adapt/modify/override the tooling and make it do what you want. Further, many times the tooling is there to keep you from doing things you probably should not be doing, and this kind of strict, opinionated, best practice enforcing philosophy has gotten me out of trouble at times, and I think it makes it much easier for engineers to move between Rails codebases and start being productive even faster.

I've done plenty of Node/JS/React and I honestly do not understand how people can prefer to use these stacks over Rails. For full stack web dev, Rails is such a pleasant place to work every day.
Actually, compensation is based on what the company has to pay. There are some other rules, like they have to (overall) pay less than they make from the output. But in general, a company never pays their employees more than they think they have to.

10x programmers don't make 10x the pay. They might make slightly more, but not even 2x what a 1x programmer (of the same level, no comparing seniors to juniors) makes at the same company.
Lecture 16: Template Metaprogramming [pdf]
I think requirements have generally shifted quite bit from what plain html can do, if that's what you mean with "hypermedia". Though true, there's probably a growing understanding that one doesn't need React on every website. So maybe it'll rather be more refined understanding of when to use certain technologies.
You misread. They're using Al, he's in Chennai and on call 24/7.
Nakamoto et al. vs. The United States et al.
FWIW, I always write tests for my changes, as long as they have any impact on behaviour (i.e. not writing tests for adding a little logging or metrics, but am for any new or modified business logic). Every single dev having a strong commitment to automated testing is a requirement for an environment where you can sometimes get away without manual testing.

For any changes where it's not obvious that it'll work in practice, despite the tests, I also run the full app locally, and test manually. Or for any UI changes, obviously. For backend changes, for some codebases, running the full app locally is required for ANY change, period - hard to reason about code, little-to-no type safety, weak overall test coverage, etc. But if you have a simple backend change in an easy to reason about code base, that has great guardrails (great automated test coverage, great monitoring/alerts, canary deploys with auto-rollback), there really is not much reason to actually run the full app for a simple change, which is a nice productivity boost. Just make the tweak, write/modify tests if necessary, and if everything passes on CI, you're good to go.

For the 8 years before my current job, I was working in environments that weren't safe enough to do this ever, and was horrified when devs would merge without actually manually testing their changes. But my current company/environment has a codebase with strong typing and nice abstractions/local reasoning, great automated test coverage, and great monitoring/alerts and canary deploys with auto-rollback. Took me a bit, but I've embraced the "no need to run the app for simple changes" approach, and it works great in this environment - highly productive and still safe enough.
That's a good point. FB/Meta did a blog post talking about the tech. There are some failure examples there:

https://ai.facebook.com/blog/using-ai-to-bring-childrens-dra...
I don't really find myself missing static types with LiveView, I just write some Ecto Changesets and anything invalid gets bounced back to the browser with an error. That plus some DB constraints and some structural types in function signatures gives you a ton of safety. I basically never see any errors coming from the CRUD stuff, only the more complicated pieces that touch old parts of the app.
I want to be ambitious and enjoy my work, but most of it is REST or similar level work. Those rare times I have an interesting project I end up stuck waiting for information or eventually code review (for days).

Nowadays I just want out. I'll get that feeling doing my own thing with no blockers but time and myself. I'm not at all convinced this is generally possible at any company (based on what I've heard from friends and read on HN and elsewhere). There's always something in the way.
The picture I was trying to paint is much more radical than that. There are emergent phenomenon that come from less judgement and more openness that I would argue can subvert the paradigm you're describing. But yeah, part of the idea is that if we remove the endless barriers we have embraced that deny us sex and intimacy, we will all have access to more sex and intimacy. We may also find that we want more and different kinds of sex and intimacy, which may in many cases lead to a reduced demand for straight sex.
Also a linked 1h talk at cppcon that inspired this lecture

https://youtu.be/tiAVWcjIF6o
I once met a "Senior Manager" at a very large and successful company with only 1 responsibility: compile a quarterly report by consolidating a large set of monthly reports.
Terminal pass-through printing being used in 2018.

https://www.techrepublic.com/forums/discussions/passthrough-...
Same experience with a medium sized Rails project here. I joyfully ejected after several months, I needed a detox from the untyped mess, every singe library was different, there were no coherent apis/interfaces at all. All Rails patterns were replaced with some random "smarter" counterparts, dry-rb here, some "better" orm developed in a shack there, all glued together. I recognized it's not the issue with Rails per se, it's the Ruby devs culture and I'm not compatible with it (even though the team was quite good, just a lot of cruft to deal with).
Pretty sure an anthropologist would disagree with you there. Humans for the most part have not been monogamous until recently. There are many historical examples of men who have sex with multiple women in the tribe and many examples of women who have sex with other men besides their partner. And yes, my language was intentional to point out that historically it was expected that a woman had one partner but a man could have many.

Not all societies today even value monogamy. In France some consider the President weak if he doesn't have at least one mistress. And in fact the same thing in America.
Ask HN: How have embedded systems engineers dealt with working from home?
After 2020, companies had to go fully remote. One thing I was wondering: how embedded systems engineers managed to do this transition?

I did internship in this field and worked for a year with embedded software, before I moved into backend engineering. From what I recall, in some occasions, I was okay with just a development kit. But there were many other ones that I needed more than that (probes and testing infrastructure are the ones on the top of my mind).

How did tech companies, especially hardware ones, dealt with this? I really can't see how a company like Apple or Sony managed to keep releasing new devices with a complete remote workforce.

Please, enlighten me : )
> either we all start giving away the Thing until it’s no longer a rare commodity, or we invent amazing sex robots with good mobile joint movements and realistic audio sounds.

It will always be a rare commodity because sex is costlier for women (because of pregnancy). These discussions seem to always miss that basic game-theoretic dynamic.
> Foreign leaders staying in the hotel chain of the sitting President is pretty blatant corruption.

That's about the foreign emoluments clause (which already applies to other public officials including Congress), not the Presidential (domestic) emoluments clause, which is about the President getting money or other material benefit other than those legally due to his office from the federal or state government (which was also an issue with Trump's DC hotel, for many reasons, just not “foreign leaders staying there”.)
Why is aging "social hell" for women? Because other people don't treat them the way they hope to be treated?

Fwiw, I agree with you that older women face an uphill battle in society. It's just curious that you extend sympathy to them but not others.
The List, is a list in descending order
The story confuses the difference between radiation and contamination.
Hi, I'm one of these people.

I used Go for about six months and eventually abandoned it to pursue Rust, a decision I've been extremely satisfied with. The longer I used Go, the more I grew to hate it and error handling was one component of that.

Well over half of Go source code in practice is dealing with errors, and somehow the Go ecosystem has convinced themselves that "verbose" is the same as "explicit" when it doesn't need to be. The worst problem isn't that it's just a lot of excess code, it's that it makes all sorts of very simple and common programming tasks ridiculously unwieldy. The most obvious example is calling a fallible method, doing something to the result, and returning it (or the error). This is one single character in Rust but a minimum of four lines—with branching—of copy-pasted boilerplate in Go. Which isn't a lot in the abstract, but then you multiply that by hundreds of times and now I have read, lex, parse, and mentally discard the majority of pages of source code that's doing something that could be done in ten lines with a massive incerase of clarity in a more reasonable language.

You've probably "never seen" us because we felt very let down by the overpromise and underdelivery of go and we left.
this looks like a fantastic tool! would love to use this in some Python CLI's to help users understand the progress
Was thinking the formulation sounded weird, as from this naive armchair that seems like a straight mutual information problem. https://en.wikipedia.org/wiki/Mutual_information

The red/blue beads thing is a metaphor for two random variables (red, blue) and the question seems to be about the information between them. Evenness and oddness is really a proxy for the effect of prior states on future ones. It's very likely I have a comedic misunderstanding of this, but if someone would like to provide the requisite humiliation, I'd be interested in why this interpretation is wrong.
Wrote Go code daily for quite some time, also tried Rust.

I like Go because of the tooling and simplicity of the language, it's easy to learn and explain.

Rust has the borrow checker has a corner stone. The concept mutability and references is easier to understand if you are coming from the c/c++ side of things
Two things.

First, it’s natural to expect children to be more traumatized by an event than adults.

Secondly, the period before and after a peak is a slope, not a sudden drop into nothingness. This means that a thirty year old woman is not “sexually invisible”. Similarly 40 year old men aren’t invisible either even though they supposedly peaked at 30.
Agreed. Scaling application servers is "easy" since they can be scaled horizontally; in other words, you can just throw more hardware at the problem. Scaling databases is "hard" because of CAP/PACELC-type issues in maintaining consistency, and because some DBs (like Postgres) don't have good support for horizontal scaling.
What's your favorite?
Tim O'Reilly: Let’s Open Big Tech’s Financial Black Box
The shouldn’t flow to the treasury. They should go directly back to the public.
That’s actually fascinating, because this official login solution exists, and it seems very nice: login.gov. It’s from the GSA which seems to be doing some good work.

I wonder how id.me differs, and how we haven’t centralized on one solution yet
From the TFA -

This is not for http://, https://, file:// links. This is specifically for microsoft-edge:// links, which I've never seen.

I think this applies only for Progressive Web Apps (PWAs).

I'm wondering how many of the commentators here have actual read the article.
Canada Post, the equivalent of the USPS in Canada, offers exactly this service [1]

I've used it for Know-Your-Client type stuff with banks, but it is theoretically open to most if not all businesses. Every time I've needed to interact with it, it's been a straightforward process as a consumer.

[1]: https://www.canadapost-postescanada.ca/cpc/en/business/posta...
Not to say that it's "right" as that is a complex question, but this double standard is logical from a biological point of view when taking reproduction into account. I wouldn't say homophobia is the only explanation.
do we need that labor pool considering we are progressing in technology? 100 years ago there were no factories we see today etc. But day by day with technological advancement we are automating lot of things. So I really don't think we need that much labor we required yesterday.

Is population problem really a big deal considering we already have a big elephant in room already like climate change, scarcity of resources, poverty, water crisis?
I don't think DefiPulse has everything. Here's a few more off the top of my head, though I'm sure there is more:
- $5.5 billion (TVL on Eth L2s via L2Beat)
- $4 billion (ETH 2.0 staking contract)
- $17 billion (Polkadot staking)
- $16.5 billion (Cardano staking)
- $36 billion (Solana staking)
> I also often don't understand the technical details other developers discuss in meetings.

I often worry about this, but unless you're at the Staff+ level, I think the chances of you knowing the intricate details of ~other~ peoples' work is low. And that's probably not a problem.

> makes me wish I'd tried a bit harder at bullshitting.

Honestly, I'd highly encourage it (a little). Being able to market yourself and your skills is very valuable.
I see this regularly at small companies, too. They add process they think is necessary but don't have the human resources necessary to ensure these don't become blockers.
As always, mentioning that Your Mileage May Vary (YMMV) puts the emphasis/decision on the people facing this or that situation rather than blindly applying advice found on the Internet.

And rightfully so :)
It's also because COBOL and languages of that era had fixed widths for most of the "records" they had, for good reasons that many modern programmers are rediscovering every day...
A fairly meaningless statement in reality, since it’s not how most people behave.
Yeah...

Anyone know of any that aren't? Most things around that I know of are from people getting banned from reddit and building their own.

Just checked out tildes.net, that one seems pretty ok at a first glance.
What's gonna be really exciting for people like this is when CTVT, like HIV, eventually transmits to humans.
I wonder if some people on my team even work 1-2 hours a day honestly.

What I've found for myself is this greatly demotivates me. Why am I putting in 6-8 hours of pure coding a day when I see the guy next to me doing 1 hour of work and getting payed 2x as much?

I legit have an ic7 on a sister team that has made 40 diffs in the past 2 years, I don't think a single one has been > 50 LoC and it was mostly config changes. Crazy world we live in.
Someone: Operating systems are too complicated.

Docker: rebuilds virtualized operating system
https://tabby.sh/ was the other.
The 5->10 hours a week is definitely on the extreme end of laziness.

However, I do think if you are doing the full 40+ hours only working you are likely heading towards burnout. IMO, 5->6 hours of work in an 8 hour work day is both normal and acceptable to keep people from burning out and ultimately dropping to the 5->10 hour a week range.
> It could be a meaningful technological shift if a lot of the financial infrastructure goes decentralized

It's important to note that “DeFi” is more centralised than our existing financial infrastructure. (Also, our existing infrastructure mostly uses open, public, well-known standards with many implementations; most DeFi stuff… documents how it currently works, I guess? Though it's hard to find that documentation.)
He occasionally makes YouTube videos on Bitcoin related topics; you can see his desk space in most of them.
The article's figures include the centralized Turkish exchange which made off with ~2.6B , so I don't think it's fair to consider it the same kind of thing.