skysight-inc/HackerNews huggingface dataset:
I'm not sure the creators of Unix would have agreed. Unix was a step in a very different direction at the time. It was a reaction to baroque operating systems that did a lot of stuff and were quite complex. The key to Unix is simplicity and, if you shave it down, that it was really a system interface definition - which enabled other people to create Unixen by offering the same system call interface with the same semantics.

It was neither free, nor do I think the timing played much of a role since there wasn't any comparable OS being made at the time. The important bit of Unix was a set of key ideas.
All valid reasons, however as proven by USB Armory Go's bare metal unikernel, had the people behind Go's introduction stayed on the team, battling for it, maybe those issues would have been sorted out with Go still in the picture, instead of a rewrite.

Similar to Longhorn/Midori versus Android, on one side Microsoft WinDev politics managed to kill any effort to use .NET instead of COM/C++, on the other side Google teams collaborated to actually ship a managed OS, nowadays used by billions of people across the world.

On both cases, politics and product management vision won over relevance of the related technical stacks.

I always take with a grain of salt why A is better than B, only on technical matters.
Tests are not about bugs. Tests are about code correctness. If applying tests, which I personally do while I write my production code, is catching bugs then that is of course a positive side effect. I write classic unit tests for the code where it's possible but do I have external dependencies I either mock them or stub them.

While writing tests alongside writing production code you might become aware of code that does not conform to your own qualitative measurements. SRP, DRY etc. That process, writing tests while you write porduction code, imo, has a tendency to better your design. But I never look at design as being done, I look at it as being good enough for the time being.

If you write test after you write you write your production code, bettering your design becomes more difficult, since the code is already written and you might need to make larger changes that will adhere to how you really wanted the code to look like.

Tests should give you confidence. Without them you are clueless and have no confidence when you start making changes. You cannot juggle with, on a cognitive level, that if you apply a change to your code, that whings will just work. Tests gives you that confidence because it gives you fast feedback.

You can not argue that removing dependencies and therefor mocking is a possibility. Unless of course you have no dependencies, like the calculatur or greetings funtion in the post.

You can move your dependencies around and perhaps invert them, but you cannot remove them. A good example is that instead of injecting external dependencies to your own classes, inject objects which represent a dependency in isolation.

Then you can control the isolated object which is a representation of an external dependency but do it without mocking.

The best book I have read about testing is Vladimir Khorikov's https://www.amazon.com/gp/product/1617296279/ref=as_li_tl?ie...
> Saying static typing is "hype" is like saying "adding a handle to a coffee mug makes it easier to hold" is hype.

I think so too, but that doesn't mean it's not controversial.

There are plenty of commenters who will happily say that it takes too long to put a handle onto a coffee mug. Handle-less mugs will get to market first! Besides, you spend too long fighting the handle.
I can just see it now. Massacre. All the oil from the pan in the plate. Set the hot pan down on the counter top.
Just a sidebar on the word "civilian". Police offices in the US like to call member of the public "civilians", but they themselves are civilians as they do not fall under the military code of justice. Unless you want to argue that they are an occupying force that is in armed conflict with the population and should be treated as combatants under the Geneva Conventions...
To the extent that Go has features that no other popular language has, it is not influential. To the extent to which it invented those things, it's not influential. And that's why he didn't make that claim, he made a much broader one. The only problem is, if you make the broader one, it's obvious it's F#/C# that's been influential.
I did not know that. Wow nice. Having so many SSIDs is drawing attention to all the equipment in my flat.

However I guess this feature is WPA3 only which means I'll still need the SSIDs for years to come :'(
If I wasn't sat here trying to figure out why a Transformer for a Provider is causing a circular evaluation when it's queried, but only when called from the Kotlin DSL, I'd be a lot more inclined to agree with you. At least Gradle 8.6-rc-1 gives a nice error message instead of just failing with a StackOverflowError.

I'm actually kind of a Gradle fan, but it's hard sometimes.
The Palm Pre had the best mobile typing experience I have ever had. I tested a lot of different stuff (Blackberries, various weird looking Nokias), but something about the Palm Pre was just... better. It had the perfect amount of resistance, the keys were well defined and had a nice rubber touch.
Agree that ComfyUI Manager is super helpful for custom nodes, Yup, haven't found anything that'd work out of the box yet. It'd be helpful to even just have a marketplace where you can bring your own API and sell calls from the platform, abstracting away the user management and billing. I was able to put some of my ComfyUI workflows behind an API so that it runs on 'serverless' GPUs, but am still stuck with the rest of the stack to build from the ground up.
Whenever there is a new technology, people get caught up on how the new thing doesn't work exactly like the old thing and get hung up on small differences. With online shopping, it was "it will never work if I can't try on clothes". With iPhones, it was "it will never work without a keyboard." But in the end, the new thing does new things which creates a new market.

Electric cars have all sorts of awesome features that ICE cars don't have. You don't have the same quick refueling but you have lots of other advantages. They can act as a giant battery for your house. You can keep them charged at home with no effort and never go to a gas station again. If there's a gas shortage, you can still power them easily without waiting in lines. If you live in a 220v country, you can literally just plug them into a wall anywhere if you run out of power or want to charge overnight. Most electric cars let you turn them on and heat them up remotely with no need to leave the engine running and with no fear of generating fumes in an enclosed space.
Finally, thank you so much!
Was it so difficult?
Isn't 7 lines of mathematical notation way better than pages of qualitative pub talking?
I don't really understand these ML researchers, it always looks like they have never studied mathematics at all.
How I set up my new MacBook
Open for suggestions/criticisms.
As a cyclist it seems like an attractive solution as a dash-cam equivalent. That's not really for security but for peace of mind with insurance claims.
There's a beautiful walk between Folkestone and Dover that somehow even people who live in Kent aren't aware of. It's especially good for geeky types as there is some lovely infrastructure to see and learn about. The railway snakes along the coastline, weaving in and out of the cliffs. You can walk below the railway or up on the cliff above it. There are signs of early attempts at a channel tunnel from the 1800s and, of course, the real channel tunnel. In particular Samphire Hoe which was created using the earth removed from the tunnel and now houses ventilation fans for the tunnel.
Doing it in real life ONCE is quite fun. The great things about computers is that you can solve a problem once and let the machine repeat it.

Having to do it everyday for years and not being able to do other things because of that is not fun at all.
Exactly my path as well. Was on ant, ant got cumbersome to maintain especially in big projects. Maven came up, "oh let's try that"! "But it's so painfully restrictive!", tried Gradle, eventually noticed that it's the same gunk as ant, just looking less like "programming in XML". Then ended up diving deep enough into Maven to learn how to make it behave and do what I want it to do.

Nowadays, in the most extreme case I write a new Maven plugin. But in 99% of cases I can come up with a solution using existing stuff. It's not always the straightforward solution, but in the long term it's usually better to maintain than what I'd cooked up with an imperative system like Gradle.
I forgot to mention that writing tests has, imo, a lot to do about thinking about what production code you write.

https://fs.blog/writing-to-think/
Yeah, they managed to recreate the advantages and disadvantages of Modula-3's typing system within three decades. Groundbreaking.
> the moment you put a MOCK in that code is waste.

I disagree. I mock the interfaces to other components that have clearly defined output in a clean architecture to properly unit test (i.e. a use case). Everything else causes components to be mixed and things to be tested again and again, causing complex and glued together tests.

It all depends on proper architecture, which is hard to get right though. We're using kotlin (sealed classes ftw), hexagonal arch + ddd (use cases) and graphql/rest on top. Everything split up by gradle multi modules with architecture tests to verify that modules have not been mixed. We also have a domain module with plain kotlin that implements business logic free of implementation details. With this high separation of concerns unit testing is the only thing you need to do (automated).
> It wasn't any disrespect, at least I don't have any spiritual practice to disrespect, but rather the cavalier attitude against a reasonable warning.

Sorry for misreading you, I was presumptive.
Design by contract, i.e. preconditions and postconditions, is also a good complement to unit tests.

int f(int n)
{
int result;

assert(n >= 0); /*precondition*/
...
assert(result >= 0); /*postcondition*/
return result;
}
Biscuits, chips, "pudding" or flapjacks are also completely different things in different countries.

It's the opposite of the scone situation; my wife pronounces that "scone"... whereas I always pronounced it "scone". Potato/Potato I guess. :P
C# not only has channels, it has async/await, which he concedes is the actually popular form of concurrency in that others have adopted it.
We have frequent daily power cuts here lasting 2 hours - this feature would be a killer for folks here but sadly EV's except for a few niche luxury models are not sold here.

Golden marketing opportunity for BYD which is not well known in the west.
I think it's achievable with a nation state net but more challenging. Given kids at least up to replacement rates are usually net positive, society will have to economically reflect them as a profit center rather than hogging most of the gains and artificially shunting them as cost center to producers of children.

Although if it were me, well, I'd just leave the kids the hell alone and let them decide who they want to help.
Considering the source, is this a real poster, or…?
For too long, web browsers have dominated the market for applications that are consumed by document readers, glad to see some competition at last.
OP here, the switches we used are push-button Berker switches. I can't say I'm 100% happy with them, they look nice and are tactile but they are the "toggle" type - push and hold to either dim or brighten (never really know which) then again for the other direction, or quick push for on/off. My other annoyance is that sometimes a quick push does not register, but I don't know if this is because of the switch or because of the Shelly dimmer... I think more likely it's the dimmer.
Of course. But that's what were discussing here right, ways people might commit fraud. If people can popup businesses for fake, fraudulent jobs, I wouldn't think this kind of fraud is out for them either. And in some jurisdictions, being hard to trace as a business beneficiary is actually not difficult.

It surprised me when I ran a small business my bank didn't even require me to file the signatures up front. I just typed in peoples IBAN, the amount, and got it. They never asked for paperwork ever. Naturally, I didn't commit a crime, but I'm surprised with the trust.

So, yes, keep your IBAN secret, it can be enough for someone with criminal intent.
> Are cartoon physics insulting kids intelligence?

dclowd9901 already said the issue is when it's "just lazy storytelling". Pixar shows you can tell great stories with cartoon physics.

You don't eat only sugar. You don't eat only carbs. You don't eat only protein. Your body needs a mix.

Many people want their kids to have a healthy diet. Saying Nutella is a "sometimes food" is not the same as saying Nutella is "bad", or that it's a "never food."

Tom & Jerry is a sometimes food. Other shows exercise a different range of critical skills.

I was gobsmaked when I saw a clip from Mr. Rogers where Daniel Striped Tiger asks Lady Aber­lin "What does assas­si­na­tion mean?", in a special episode created after the assassination of RFK. https://www.youtube.com/watch?v=pQv0ZtpRdNk And Mr. Rogers could tackle racism head-on, like https://www.youtube.com/watch?v=v4recJ6qXyk in an era when blacks were prohibited or physically attacked for trying to go to "white" pools.

Bluey could take on these sorts of topics for kids, in an age appropriate way. Tom&Jerry could not.

Nor could Blippi, so it's not just cartoon physics that's the issue.

But Mr. Rogers couldn't pull off the classic "coyote paints a picture in a wall, Road Runner enters the picture and speeds off into the distance, coyote tries and crashes into the wall" gag, nor should it. I don't think it's a good idea for kids to only watch Mr. Rogers-type shows either.

> kids are more interested in stuff which is surprising

Strange then that kids' cartoons are often so formulaic.

"The Animal Mechanicals are sent to a new floating island to resolve a problem. The team comes up with a plan, and each team member gets to use their special abilities to help out. There are problems along the way, but they are resolved and everyone is happy at the end."

"Something goes wrong. The Paw Patrol are called to help. Ryder comes up with a plan, the pups use their special abilities to help out. There are problems along the way, but they are resolved and everyone is happy at the end. Except for Mayor Humdinger."
be clear at a glance
I don’t remember where I read this (think it was some published paper) but I was building some audio streaming thing on top of WebRTC and there was an estimate that 60% of people would be able to do p2p.
No way is that simple.

your rules would state "application specific data" would not reside in appdata even though those exact terms are there. it's the opposite of self-documenting
> No language launches perfectly.

There's a gulf between "not launching perfectly" and launching with obvious, blatant deficiencies.

Go did the latter. Generics were always going to have to be implemented eventually, at least two languages in basically the space Go was targeting had had to bite that bullet in the decade before it was published. Support for third-party external dependencies only made that more dire.

Instead of doing the work up-front and launching with generics, they decided to launch with ad-hoc generic builtins and "lalala can't hear you" for a decade, then finally implement half-assed generics.
I don't think it would work well - once you start recording it's too late
I think I want my writing to reflect how I talk or think about it. So if the spoken sentence is "specification is a half millimetre" then write with ½ instead of "0.5" because the former will be read out correctly.
> While he recommends leveraging debt to buy assets, he disapproves of taking out a loan to buy materialistic items that won’t increase in value or pay dividends.

> “A lot of people use debt to buy liabilities,” he said. “I drive a Ferrari. Guess what? It’s paid off 100% because it’s a liability. I drive a Rolls-Royce. It’s paid off 100% because it’s a liability.”

There's your answer. And this is actually sound advice. You don't want to accrue interest payments on depreciables. But in the current money printing macro environment, it makes sense to leverage, depending on your time horizon and the prevailing interest rates.
the x/ packages languish a lot, the problem is they follow a development model that slows the rate at which new contributors succeed to send patches

The stdlib crypto package I would describe as another of Go's big successes. OpenSSL has been a disaster for a very long time, and Go and perhaps most significantly agl managed to build and ship a very broadly exercised alternative implementation with an average very high quality, particularly from the perspective of having significantly fewer footguns in the public API.
> With online shopping, it was "it will never work if I can't try on clothes". But in the end, the new thing does new things which creates a new market.

At what cost, though? The effort of online fashion retailers and postal services to deal with returns is insane, and by far not all clothing can be shipped to customers as new, so it has to be re-sold as secondhand or destroyed. Yes, it's all priced in, but it's still insane from a holistic view on society.
>It’s not. In 2025 basically all US EVs sold are planned to be on NACS.

And on the European side it'll all be CCS....hence split world...just like

>This is starting to feel like 110v vs 240v.
Well hopefully it improves it. Heh :)
I may already be able to talk to Copilot - I've yet to try since I heard they were adding that feature.

I think this is more symbolic than functional necessarily. The last time they made a change to keyboards was to add the windows key when they were launching 95 and at the time they were essentially declaring that windows was a really big deal, so big that it would justify a button - bc it was going to stay that way. In 94 that may have seemed uncertain but...

That was 30 years ago. By their own statements they are comparing copilot to windows itself as far as significance.

Microsoft is all in on this.
std::span should apply, but std::optional is at least as large as the type it wraps.
If you're talking about the blog, it's an open source Zola theme https://github.com/not-matthias/apollo (the original site https://secret.club which it's based on/inspired by is closed source though)
started using RSS feeds a few months ago, they're still widely supported and there are JSON scrapers for those
sites that don't. The idea of "reading N accounts" to get some info or some algorithmic
soup of "popular stuff i tangentially show interest in" doesn't even compare to curated RSS feeds
organized into groups. The unpopular, rare and obscure stuff can't compete with algorithmically
optimal SEO-friendly hype-tagged social media junk in the "common prole-feed" of giant websites.
Just a fun anecdote on end-to-end testing I did 20 years ago while working on the compression of images.

Some parts of the algorithm were easy to test, others very hard. On the easy part was loading and saving the file. I tried to test as best as I could, but the lossy part was not really tested.

Then time to benchmark the algo on some images.
The results were kind of OK, but some images compressed much better than others at low bit-rate, while the content did not look much different.

On square images, everything was fine.
On rectangular ones, at high-bit rates it was somewhat fine, but strange patterns like ghosts of another part on the image started to appear for lower and lower bit rates.

Of course, I searched on the mostly algorithmic parts what was going on, and failed.
Only after a holiday break and fresh eyes did I found the root cause: inversion of height and width in some part of the loading AND saving.

I had "end to end" test of the loading and saving, but the error was symmetric, so undetected. Young engineer error...
Which matches up with large format sheet film and typically close to medium format. But is actually a significantly different aspect ratio from 35mm which became almost universal over time.
If you enjoy Hitchhiker's Guide style comedy radio plays, I'd recommend the slightly fictionalised version of this story available on the BBC:

https://www.bbc.co.uk/programmes/p06y18n2
> TDD makes it painful to write tightly coupled code, and that's the point.

That's also the problem with TDD. Another word for "tightly coupled code" is "cohesive code". There's a tradeoff between coupling and cohesion. The problem with TDD is that it can make people decouple cohesive code just to make it testable. I have seen this many times where the only use of some abstraction/indirection was the test. These abstractions/decouplings then mount up to make the codebase much more difficult to understand and maintain than a simple cohesive codebase (with decouplings only where necessary).
I think parent is confused with NRVO typically not being triggered when returning a function argument.
You may be surprised to note that neither the FAA nor EASA mention running engines at all in the requirements for emergency exits and associated hardware (ETSO-C69c, 14CFR25.810).
So the thing is - when you start at a new company you also need to submit all kinds of personal data - to the company you are starting in. I am a bit fuzzy on the details here but I think the data needed to open a bank account might be the same.

She handed it all over to the police and they are on it now. I, too, hope that the money can be traced.
Kohezion is a no-code development platform for internal business apps. From form builder, simple CRM and project management to ERP and enterprise document management, Kohezion empowers organizations to build mission critical business applications without the need to involve developers, accelerating digital transformation and automating manual business processes.
No worries. If anything it means I somehow failed to get my point across in the first go. Much to learn. Thanks for giving me a chance to clarify.
Hey there, Author here,

I agree — I should have done a better job writing the copy.

Here are some tasks you can accomplish with an AI employe:

- While I haven't optimized for testing, you can perform end-to-end tests simply by describing it. If the UI is complex, the AI employe will hallucinate; just click 'start recording' and demonstrate the tasks. It only records HTML changes, not the screen, microphone, or camera. and you don't have to worry about IDs or selectors—the AI employe will take care of it.

- Tasks related to OCR, like extracting data from PDFs, emails, and transferring it to CRMs/ERPs.

- Summarization tasks; for ex, there's a workflow example in AI employe where it automatically summarizes Hacker News comments for the website you're browsing. It automatically do the HN search, clicking the relevant link, and summarize the comments.

Since there are a couple of things an AI employe can do, I am simply confused about how to position it. Any feedback on how to position it is most welcome.
Because it’s none of their business. An interview is there to evaluate a candidate’s suitability for a role, not to dig into their personal life. What they did at work is relevant, what they did when not working is private. You wouldn’t ask what someone did on a Saturday night.

Maybe they were sick, maybe they were pregnant, maybe they were looking after a dying relative, maybe they were backpacking across South America, maybe they were sitting at home watching every episode of Star Trek, what people do in their own time is a private matter.
Perhaps Shinkanzen was an old Polish train between Krakow and Zakopane: 120 km in up to 8 hours.
This was the 1970s, baby. We had Supergraphics!

https://clickamericana.com/topics/home-garden/supergraphics-...
BYD is fairly well known in Europe? They sold 50% more cars than Tesla last year, so they’re not exactly a small startup.