skysight-inc/HackerNews huggingface dataset:
The biggest issue with Dart IMHO is not so much the language itself, but the ecosystem.

For the record, Swift suffers from this problem as well. Kotlin only avoids it because of Java interop, although even this becomes complicated because of Google’s half-assed implementation of Java on Android.

I think this is one of the biggest reasons to reach for JavaScript instead. It has a lot of flaws, but it has a huge ecosystem that works nearly everywhere.
RFC, in its earlier days, was not as rigid as it is now. You get standards written like essays (good for figuring out why, not quite good for figuring out how to do something) and regular essays. Check out more from the Informational category:

* RFC 1121 "Act One - The Poems". https://www.rfc-editor.org/rfc/rfc1121

* RFC 1983 "Internet Users' Glossary" https://www.rfc-editor.org/rfc/rfc1983

* RFC 2468 "I REMEMBER IANA" https://www.rfc-editor.org/rfc/rfc2468.html - Yes, people kept having fun after RFC 2119.

More goodies at https://www.rfc-editor.org/search/rfc_search_detail.php?sort.... A lot of the April Fool's RFCs are Informational too.

The even older categorized class contains more essays. https://www.rfc-editor.org/search/rfc_search_detail.php?sort...

See also: https://en.wikipedia.org/wiki/Request_for_Comments#History. RFC started out informal!
Is a planarity testing algorithm explained in the book?

Also, methods to transform any graph into a planar graph with some cost function?

This is what I would be most interested in.
I spent quite some cycles into flutter|dart, ended up with React Native for mobile and wxWidgets for cross platform desktop GUI(electron.js is too fat for me and wxWidgets 3.2 looks decent).

RN(javascript) and wxWidgets(c++) are both job friendly, unlike Dart, which is a language I actually enjoy, but there are not a lot jobs for it anywhere.
You could just use a better diff tool. Git itself is format-agnostic.
Virgin Media customers threaten to not renew deals over email problems
Maybe look at second hand HP Microserver's on Ebay (or similar)?

The ancient G7 ("Generation 7") ones are dirty cheap, fit 4X SATA hard drives, and use something like 12 watts of power.

The newer G8 ("Generation 8") ones are significantly higher performance, but also draw a lot more power. Socketed cpu's though, so they can be changed (as I've done). :)

They don't have in-built battery backup though, unlike laptops.
My experience is that learning a new language -at a basic level- can be done quickly (like a couple of weeks, not days).

But learning it at an advanced level, is a whole different matter.

I've been writing Swift since, literally, a few hours after it was announced, in 2014. I write Swift every day (like, seven days a week), and have been, since that first day.

I feel as if I have only had "mastery" of the language for the last couple of years. There's still plenty for me to learn, and they keep adding more stuff.

But the language isn't the big deal. The deal for me, is the fundamental SDK/API/Framework. That has been an ongoing project since 1986. As soon as I learn one API, they change it up (and sometimes, the entire OS).

During that time, I've written in 68K ASM, Pascal, Object Pascal, C, C+- (the weird THINK C variant), C++. ObjC, and Swift. I've worked with MacApp, OpenDoc(!), Think Libraries (Pascal and C), PowerPlant, and Cocoa (and its expression in iOS, WatchOS, AppKit, and TVOS).

I've always considered hiring folks to be an investment. As a manager, I always looked for folks that had the fundamentals down, and assumed that I could train them into what we need. Most of the work we did, was way beyond anything you'd find in textbooks. I was under no illusion that I could hire folks that would be able to start on it right away.

That was why my team was always one that I wanted to keep whole and cohesive, over many years. I can't even imagine today's 18-month engineer lifetime. I kept my engineers for many years, and that wasn't easy.
Channels are also not great when you want to break off / cancel iteration.

The overhead also compounds when you compose / chain iterators.

Plus the "lag" they induce due to context switching, although I think I saw an optimisation (proposal) where the runtime would directly switch from one routine to the other in some cases of channel interactions? Or am I thinking of an other language entirely?
I would be a bit cautious with that statement. Sure, your local general practitioner may not be a scientist, but quite a lot of medical doctors attached to major research hospitals and medical schools are both physicians and scientists who not only treat patients but also conduct research on the efficacy of treatment and publish papers on this.
I wish tRPC could interact with Go app but that's limited to TypeScript.
The nature is nice. Harper's Ferry is one of the most beautiful places I've ever been in my life. But it's not much nicer than any other Blue Ridge state all the way down to Tennessee and Georgia. Meanwhile, the town life, at least as of 20 years ago, is desolate. My best friend from college grew up in West Virginia, and I spent a week with him there before he moved to LA to become a television writer back in 2001. I don't know that I've seen a place more falling apart. Houses collapsed, abandoned. Weird paint splotches that looked like blood stains on houses that were still occupied. Every single lawn had a Camaro body with no engine and no tires propped up on cinder blocks. Other than coal mining, the only employer in this guy's town, which is where he worked, was some kind of direct mailing marketing operation that paid minimum wage.

The only upside, if you're truly poor, is you could rent a reasonable sized place for $100 a month.
You are right that this is probably not the worst thing they did. I’m absolutely sure the US armed forces are a highly sought playground for psychopaths and people with sadistic tendencies. Furthermore military tends to attract people with a predisposition for authoritarian and/or facist mindset. We saw the snapshots of unspeakable torture - made by people that were so entertained by the atrocities that they just had to make commemorative pictures of it.

But collateral damage is something else: if I blow up a house with a terrorist leader in it, weil the debris kill a bystander? It happens in every war and it’s the main reason why a ‘just war’ still can’t be fought without tainting conscience.
> 1000 conductors means there is no conductor.

1000 conductors means that there is 1000 conductors and 1000 orchestras.

They've all done their research, and they've all independently decided to have their orchestras play mostly the same songs as all the other orchestras.

They've arrived at this decision by copying what the most successful orchestras are doing, reading in orchestra magazines about best practice for orchestras, going to orchestra conferences, talking to other conductors over expensive meals and games of golf, etc

I agree it's not a conspiracy. There's no big room where all the conductors get together and all agree which songs to play.

But it's not accidental either. Each conductor is seeking the best song list, and by using the resources available to them they are all coming to similar conclusions.

I think I've tortured this metaphor enough.

I just do not want the human element to be abstracted from the equation here. Yes, I agree there's no conspiracy. Ultimately this crap is "emergent" from the systems in place. Those systems were built by humans, and then the "emergent" behavior is just humans concluding "based on this system in place this is the best set of actions I can take". Those humans then are successful so other humans try to copy them.
You're probably from Germany, the Nederlands or Denmark then. It's a common Northern European prejudice to consider southerners "lazy".
"Great Books" Lists: http://sonic.net/~rteeter/greatbks.html
That might be the case for other disciplines, but it certainly isn't for philosophy. There are no special techniques, you just read what other people have said on the subject. What else is there?
As long as there are no board schematics provided, things are not reparable. Just certain modules containing 100s-1000s of components can be changed (and thrown directly into the trash).
Finite-WASM: Cheating a little to solve the halting problem at scale
Maybe I’m special (and it was 6-10 years ago), but after becoming proficient and pretty deep in osx/ios development I took an android project and it wasn’t obvious AT ALL. If it were a new job and not a project pushed to me at the same position I had, pretty sure it would be difficult to keep it.

Of course that depends on average expectations. Some people may learn and do and relax and still outperform if these are low.
Like the conspiracies Trump's going down for!
AML works, even if it intercepts less than 1% of criminal proceeds
This is a textbook example of syntactic sugar, where a feature can be trivially transformed into simpler code that doesn't make use of the feature
Peoples preferences are not holding back the industry. If there was a linux laptop with the same hardware and software quality as the recent MBP's I'd get one in an instant. I run linux servers, I'm not unaware of how to set them up but I don't want to deal with the quirks of most linux daily drivers, so I don't.

Many linux users seem very bitter that people value Apple's offerings over linux based solutions. That this preference is somehow taking something away from them. I don't think anyone should be looked down upon because they don't value the same things that someone with a hacker/tinkerer mentality values. I think that attitude is partly what puts a lot of people off who are half in/half out of the ecosystem. I personally find it a bit tiring, and in general I'm supportive of open source and related things.
And it's fascinating how the tech-neck only affects the younger population.

My kitchen psychology theory is that it's related to privacy.

"Our" generation[0] used (and still uses) more text-based media, which is harder to get a read on with a quick glance over one's shoulder.

But with Snapchat and others where images are a huge part of the content, the users put the devices right at their chest as high as possible and crane down so that people around them can't see their screen as easily. And after doing that for long enough, it's just a habit, they do everything like that because that's the way they are used to doing it.

Maybe a privacy screen could ease the issue? The kind we have on laptops that narrow the side viewing angle so that it's completely opaque even slightly from the side.

[0] GenX/Elder Millennial is my theory about the majority age for HN
It's bifurcated. The programs in conferences with big TV deals earn money, smaller schools are probably spending money on athletics.
OpenAPI, JSON-RPC, and JSONSchema have existed for a pretty long time now. The industry has more or less standardized on JSON for data interchange and parsers/generators for JSON abound in every programming language, so it makes sense to do all this stuff with JSON.

I've never seen IDL before but I looked up some examples and it does seem useful for RPC calls. But I'm not exactly eager to switch, it looks like it's meant for a much more powerful form of RPC than I'm willing to touch, and no tooling I know of supports it.

The JS ecosystem of course is still affected by hipster disease (everyone seems to think their own wacky idea is groundbreaking). But the existence of a framework like this, built on well-established JSON-based standards shouldn't be surprising.
Sock State – Redux-Like State Container over Web Sockets for JavaScript
TL;DR: Redux-like state container over Web Sockets for Javascript, allowing for distributed computing. This has been for some projects of mine where I have multiple Javascript processes that need to communicate with each other without the usual awful workarounds.

Not-so-TL;DR:

I posted a little (awful quality) GIF preview of it's chat app example here [0].

The more detailed motivation of this is that typical Javascript build toolchains that I've seen and used all have this tendency to use multiple watchers for code builds and app process(es), using tools like concurrency [1]. These often end up plagued with race conditions and funky workarounds like debouncing.

Ever noticed when you make file changes and your app/whatever restarts a zillion times or doesn't properly restart? That's the issue Sock State was originally made to solve! Example:

Process #1: Build watch process starts, rebuilding some source code when file(s) change.

Process #2: App watch process starts, restarting when output file(s) change.

Typical flow: Source code change occurs --> #1 triggers build --> output file(s) gradually created --> #2 triggers app restart

Common issues with that:

1. Multiple debounces often required

2. Multiple file system watchers

3. App process(es) have no idea when builds start/fail

So I created Sock State for some side-projects that have particularly complex build processes in order to ensure that:

1. Build processes can publish their status updates to a centralized state store

2. Other processes can subscribe to changes of, restarting at the exact correct time, once, with no workarounds or other weird goofiness.

It's now turned into a bit more than just a glorified build status message bus, and perhaps can be something a bit more in the future.

[0] https://twitter.com/thesamhuk/status/1690318953594114048?s=2...

[1] https://www.npmjs.com/package/concurrently
Channels introduce a ton of overhead (https://syslog.ravelin.com/so-just-how-fast-are-channels-any...), plus concurrency issues, and termination concerns (they are essentially a resource leak). It's nice that you can iterate channels, but they're a terrible iteration protocol.
Likely triggering some low quality sensor. Short title, shorter text. High ratio of total comments to upvotes.
I think a strategy that might punish such misbehaved crawlers is trapping them (via invisible ahrefs perhaps ... ?) and feeding them truckloads of garbage/disinformational/esoteric/plain wrong text.

Or perhaps all crawlers regardless of respecting robots. Honestly I am not interested in improving some FAANGish algorithm with blogposts intended for my friends.
> the middle-tier private university might be a dying breed.

Given how absolutely awful the bang for your buck is on these overpriced private universities, good riddance.
Ask HN: What should be launching strategy for API Dev tool?
Hey HN,
This is my first time asking question on HN.

This side, I am Shreya, Cofounder of Firecamp.
I along with my cofounder about to launch Firecamp - https://github.com/firecamp-dev as OSS in upcoming weeks and I'm looking for guidance/suggestion from community members on

1. What should be my launching strategy?
2. Where should I post the news about the launch?
3. Any specific community/website list where I should share about the news?
4. I am thinking to write a blog on "Why we make Firecamp Opensource ? " any alternative way of sharing news you can suggest.
Any guidance on this question will be greatly appreciated.
It depends on what you value in a review. For me, a review is for me to get a glimpse at new parts of the code and learn what is coming. It is important that I understand the WHY more than the WHAT. I also put code reviews as the highest priority item in my todo list. I will always do a code review next, if there is one to do. If you send me a request, you'll have a review from me before the end of my day.

Why? Because unblocking my teammates is the most important thing I can do, and I expect the same from my teammates. I never want the reason our team is late to be "I had more important things to do" because (cliché incoming), "the is no 'I' in 'team'".

A reviewers time isn't more valuable than mine, and my time is no more valuable than anyone else (assuming accountants don't exist). If changing 3 lines is really an issue, then create a merge-tool for this workflow and add it to your git configuration file.
I would rather have type inferred literals: https://github.com/golang/go/issues/12854
I will take that 500k offer. Got a link?
Australia Urged to Extend TikTok Ban to WeChat
Why bother recombining the lines?
Is that actually true though? Most major Google apps predate Flutter. I was under the impression that a lot of their apps are either custom web view wrappers or native with shared C++ code for business logic.

Stadia and Google Pay are the only consumer facing Google apps I’m aware of that are made with Flutter.
Wow, MS/PhD Mathematics is cancelled?
Splitting User Stories – A Resource List
Similar experience to my sibling here: I've had a couple microservice shops and they really soured me on them and SOA in general.

- You have so many deploy stacks that it's literally boggling. I had to deploy code that used everything from make to GitHub CI to Jenkins to serverless just to push a single change.

- You have infinite implementations of your business logic. This is for two major reasons. First it's just hard to keep everything sync'd up; even if you've got "libbiz" you're gonna have services on various versions. But second, a core tenet of microservices is to just fork a new service for this and let other services migrate, but now you've evolved from an ecosystem of library differences to an ecosystem of service differences, which is way more complicated and expensive to maintain. It would be infinitely better if all parts of your app used the same versions of your business logic, but it will never ever happen.

- Your stacks are probably really heterogeneous ("right tool for the job"), but what that means is your devs now probably all have to know some mix of Java, Ruby, JavaScript, Python, Go, and maybe something more esoteric like Clojure or Elixir.

- Maintaining a microservice infra is way more complicated. Good luck monitoring multiple app and deploy stacks. Good luck keeping all of them up to date with security fixes. Good luck with Kubernetes and helm (or whatever). Good luck with multiple persistence systems (Postgres, Maria, Mongo, Redis, Cockroach, BigQuery, etc)

- You have to have an event bus. Boo.

- Your logging is hyper complicated now

- Because of the ecosystem around microservices, you're probably doing a lot of weird enterprisy things in your code (DDD, CQRS) that mostly only add layers of indirection or pull in more complicated dependencies, or inspire you to (against all good advice) build your own framework.

I'm not saying a monolith doesn't have problems, but I think the cons of microservices get very little play.
Rectify11 Improving upon the Windows 11 experience
It's not too hard to come up with bonus structure for engineers. Managers have bonuses for team targets at tech companies. The mistake is that those bonuses don't trickle down to the team. That's how it works in the oil field. There are bonuses for on time or early well completion. And everybody, even the newest roughneck, gets a cut of the bonus.
The LIGO/VIRGO experiments proved no such thing. You seem to have a fundamentally flawed understanding of these experiments.

That the speed of light is constant in vacuum is one of the fundamental assumptions of general relativity. The results of LIGO/VIRGO are so far fully compatible with GR.
Slow down, pardner, you're the one conflating religious studies with actual, and sometimes useful, philosophy.

What your original comment said is that people are blindly deferring to the authority of scientists, when they should instead be blindly deferring to the authority of theologians and philosophers (and presumably only those of your preferred faction).

(In the spirit of the continental philosophers, I read between the text.)
Startups Are Dying, and Venture Investors Aren’t Saving Them
The embedded device the server is running on has a very weak CPU. Since I'm trying to optimize throughput this would have quite an impact. It's fine if the first few messages are slow, the speed just has to pick up after initialization is done, which is why negotiation is okay for me. So e.g. the client requesting IDs for every method on first connection would be fine, and would keep complexity down.
Tech support chat bots will be everywhere, and they will be ridiculously more effective and efficient than the current flesh-counterparts. No more "restart your computer 5 times". It will be great, except for the edge-cases that actually require a human thought. Those cases will suck.
proof assistants have taken over?
I grew up in semi-rural Virginia and recently watched Peter Santenello's Appalachia[1] series on YT. The reality is that WV is nearly entirely rural (like Wyoming, Montana, the Dakotas), but there's little oil or gas to backfill the coal, and it's absolutely not flat enough (and is almost entirely forested) for either meaningful factory/ranch farming or much else. It doesn't benefit from interstate commerce and there's no river running through it, either. Beyond all the topographical/geographical challenges, the cities are shells of their former selves, and since both the educational attainment and financial independence of West Virginians is low, the potential for breaking out of this death spiral seems low.

All that ... and then add the fact that WV is perhaps the worst hit state by the opioid crisis.

[1]: https://www.youtube.com/watch?v=h9lSZlDJAC0&list=PLEyPgwIPkH...

Tons of natural beauty and I think the state should continue investing in tourism along the lines of what Tennessee has done for decades with the Smokies.
> Bulls and their mortal status are irrelevant.

But it’s India where they are pretty big on bovines in general and their mortal status in particular.
Do you have an example you're thinking of?
“Asynchronous Rails” – Samuel Williams (RubyConf AU 2023)
The mistake OP is referring to is spending too much time learning the wrong thing which is easy to do in the Cargo Cult that is modern Software Development.
San Franciscans Are Having Sex in Robotaxis, and Nobody Is Talking About It
When companies get bigger you likely don’t want to use spark to continue building it out
I'm still wondering why there's no regulation on this, forcing manufacturers to hand-in both the user and service manuals. I own a Kawasaki motorbike and tried to get its service manual just to understand a bit more about it, and is impossible to get it at this point unless I pay Kawasaki 100€ for its printed version (a fucking ripoff). It doesn't cost them anything to release PDFs as a courtesy to its customers.
Seemingly the president (a weird title, but okay) of that university brings in about US$750k / year - and is also noteworthy for being one of the highest paid public university presidents for some time[1] - netting US$6m for 2013 from Ohio, while stepping down from there after making some inappropriate comments.

My point is slightly tangential to the above - one might expect one of the most highly paid professionals in this role to be highly skilled, and to avoid this kind of oversight or blindsiding.

[1] https://www.forbes.com/sites/susanadams/2014/05/19/the-highe...
I don't understand the reply either. The link shows clearly how it works and that it's about managing water levels, not pond elimination. Many times these ponds are secondary, and extra care (in some case by regulations) is needed for primary ponds where beavers need deeper water to survive through winter.

Another solution I have seen is the A-frame trap which blocks the beaver from damming the culvert and takes longer for them to build around the trap. Even when they do, which they will, when the water rises it spills over. From a maintenance perspective, they are easier to clear than clog in the pipe.

As a species we had better get smart about coexisting with these creatures. Some say the water issues out west are related to the extermination beavers, and their reintroduction will do much to replenish ground water and create natural reservoirs.

But that doesn't mean we we should antagonize the humans by insisting we allow roads to wash out and flooding to occur. We need compromises.