skysight-inc/HackerNews huggingface dataset:
I actually like how this article is written, and I'm a big go fan.

I think the article has a conclusion it's trying to push to __stop using Go__. Maybe I misread it, but that's what it sounds like. Honestly though, I am fine with Go. Every language has its ups and downs.

What I like about Go is specifically what the article pointed out, the simplicity means I need to only remember a few concepts. In contrast, with Rust, or C, or C++, or Java, or C# I have to know _so many small details_ to not shoot myself in the foot.
if you read my second article: managing then absolutely sucked. You couldn't hire anyone.
Where do you see dynamic memory allocations being needed in that example? I only see locals that a good compiler can fairly easily optimize away.

Also, there’s a simple bijection between expressions with operators and two-argument function calls:

a + b * c
+(a, *(b,c))
plus(a, times(b,c))

Because of that, I don’t understand why operator overloading should give better optimization opportunities than function calls.
It's a pity you can't opt for a short quiz to prove you've tried the usual approaches.
I feel the results of this study would be culture specific.
If you are not using Windows you can use:

pip: https://pypi.org/project/pip/

pipenv: https://pipenv.pypa.io/en/latest/

poetry: https://python-poetry.org/

Which are basically the same thing.
then it is directly relevant

It isn't on HN, there are zillions of moderator comments about it. It's repetitive and a settled thing to not do.

https://news.ycombinator.com/item?id=33838162
reasoning takes into account much more contextual information. I think many would also say it's a step-by-step process in which the explicit assumptions and conclusions could be stated clearly, although I think that's probably just anthropomorphism and projection.
Correct, rational numbers are those numbers that can be represented as a ratio of integers (excluding zero as denominator). Our points agree.
It's the end of programming as we know it – again
Humans do remix stuff when we create, and copyright draws a kind of arbitrary line around when that becomes original and when it becomes derivative, mostly because if it didn't then it would be impossible for us to get new books, movies, and songs.

All copyright is a hack; it's not an ideological, internally consistent framework. It is a set of fallible legal rules we invented so that people would get paid for creating things we care about. That doesn't mean that comparisons aren't useful or that we can't extrapolate from the existing rules, but even where fair use is concerned, the actual justification isn't a logical one, it's: "if we didn't have this standard nobody would make anything." So the boundaries around fair use and what things fall into it are not being created purely based on logic or first principles.

The reason why we have copyright is because we want people to be paid for making creative work. The reason we have fair use and a standard of "originality" that treats coders/artists learning from other artists as acceptable is because if we didn't, the entire system would fall apart and nobody would be able to make new creative works.

Everything in copyright exists purely to get people to make more stuff in a sustainable way. It's an outcome-driven process.

----

More recently, there are a lot of people who argue that IP is a real, fundamental property right, but frankly, IP doesn't stand up at all if you think about it too hard. The justifications for why IP theft is theft can't be consistently generalized in a way that applies outside of the IP space. The standards for what does and doesn't count as creative aren't really consistent or based on a straightforward definition of creativity.

A lot of people would love to say that IP rights are just property rights, but... it's not all that convincing, and the history of copyright doesn't really indicate to me that the people building the laws thought of them that way.

And again, that doesn't mean that there's no consistency in copyright rules or that copyright rulings don't have implications beyond the original rulings. But it is almost always easier to think about copyright and almost always easier to understand why copyright laws are the way that they are if you approach copyright as a means to an end, and understand the existing laws not as an attempt to create an internally consistent system, but as a series of attempts throughout US history to achieve a consistent publicly beneficial outcome.

----

With that in mind, I suspect whether or not AI works count as remixing is largely going to be decided based on commercial interests, individual judges, and individual juries, possibly with input from US legislature.

"Everybody remixes" historically hasn't been the most useful argument during these debates? So I don't know how it's going to play out this time around. I vaguely suspect it's going to come down to whether or not individual pieces are recognizable? That's how we got wild copyright laws about some individual chord progressions being treated as derivative works in songs.
It opens PDFs and images. The nice thing is it is super quick and has a lot of features built-in: OCR of text in images, form filling in PDFs, signing PDFs, annotation, cropping, resizing, metadata inspection, background removal, etc for images.

The signature feature is awesome - it lets you use a trackpad or iPhone as signature pad, or capture an image. Signatures are saved for future use.

PDF support is really great - things like annotations work well and it supports proper page numbering (e.g. textbooks often have page 1 starting 10 or 20 pages in; Preview handles this) - something that built in options on windows tend to lack.
> Go is a pretty good async runtime

I think the author is in many ways right, but has missed how important the runtime is to the average programmer.

At the time of release Go made it easy to write evented IO servers, in a way that Rust, despite its superior language design (IMHO), still hasn't. This is why people continue to use it.

Other examples are PHP, a car crash of a language, but suddenly it was easy to dynamically generate a webpage, or early versions of Java, widely derided for language design, but programmers were happy to trade the virtues of elegance and efficiency for the ease of the standard library, the GC, and portability.

Give the programmers the ability to do easily something they weren't able to do prior to using your language, and they'll use it, whether PL enthusiasts are happy about that or not.
It is not all the sudden as far as I can tell.
There's a long history of Go hate, and it makes sense to me.
Go is a new(ish) and fairly popular language, which already guarantees some level of hate.
More substantially, it is an implicit argument against most things language enthusiasts like about programming languages; it's lack of static features and dynamic capability, it's non-focus on optimality in any domain, there's no attempt at uniform elegance or a motivating theory, it's just a kinda mundane procedural language that tries to solve some problems C enthusiasts had while avoiding the things that bugged them about Java and C++ (to oversimplify).
A language such as that succeeding socially and practically is borderline offensive to folks who love clever language and runtime design, who love things that can push the boundaries of performance or verifiability.

Something so apparently mundane and poorly thought getting traction is a regression in the world of software engineering, supported by a Big Evil Corp that many folks dislike.

I've also personally seen a social meta-effect of this, where in a particular space all of the language aficionados would make a point of dumping on Go whenever Go was discussed (or even when a dig at Go could be shoe-horned into another discussion), and at a certain point there are only negative discussions of it, and the snobbery (justified or not) is a form of social bonding.

Of course, there are loads of legitimate criticism to be applied to the language design, the runtime, the rollout, the marketing, the framings of the authors, but there's a persistence, a snarl, to some of the critics that seems to me to go beyond an observation of the real issues. For reasons listed above, some people seem to take hating Go quite personally.
There's one bit of jointed concrete road that I know of in the UK, a few miles where I live on the A90 near Laurencekirk.

It's bloody awful, like driving over smashed paving slabs. In my big old Range Rover with its off-road air suspension and massive reinforced tyres it's a noisy and uncomfortable couple of miles. In a modern vehicle with ultra-low profile tyres and incredibly stiff "sporty" suspension it must be like being rolled down a hill in old washing machine.

So yeah it's entirely possible that it's a very US thing, I've never seen it anywhere else.

Edit: here you can see a section, with repairs showing up as dark lines across it.

https://www.bing.com/maps?osid=55db8ed6-35d8-4916-82c3-14131...
Is it a standard retail practice to agree to a sale quantity but not a price?
Seriously though, give him a homelab
I'm sure just on this thread you'll find a ton of engineers who have saved their company millions of dollars, but they're still paid the generic wage everyone else is.
Yes, I am capable of reading an entire sentence.

I think a forest is being missed for some trees here.
Do you want an example for C++? Lock free data structures are PhD level skillset unless there is some kind of tracing GC algorithm being used.

Also RAII is great and all, yet there lots of ways to get it wrong.

Badly implemented destructors, missing virtual destructors in hierachys, throwing exceptions on destructurs, not using handle types on heap allocated data, incorrect pairing of allocators.
everything was a TLA then.
Buying somebody things for their own hobby is always risky. Trying to do it based on the idea of making it "useful" is doubly risky.

Go for the gaming console. His company will give him a laptop.
What is direct mail? If that's rhe equivalent of UPS/USPS, then that's a service, not a tangible good. A tangible good would be something more like a part used in a manufacturing process, which is where the commonality to food comes into play - food tends to have many ingredients that come together into a final product - but anything following this tangible good line, from my experience, will follow these terms.

The reason kind of seems to be to give more flexibility to the supply chain. If everyone required payment upfront to get items to shelves or lots for customers to buy, then the risk goes more fully on the last link in the chain. It appears this pattern began to spread the risk to the entire chain.
Normal retail price. They were probably hoping to wholesale it for 42 per case, which is what they’re selling it for now.
Exactly. The artifacts shown are stereotypical caching issues: Always same length (cache line size) and earlier written entries are more likely to be fully committed than later written ones but it is (seemingly) random in overall.
Spitting out the results of a bunch of experts is the opposite of reasoning. Or more correctly, it's one limited form of reasoning: an ensemble prediction made from a mixture of experts. That's not an interesting form of reasoning because literally all the decisions are encoded in the weights you apply to the experts.
I gave my 5 year old a pc running linux when she learned to read. She became interested in the command line when she saw me using it to help her find a file she had misplaced. I gave her a list of simple commands and let her explore. By the time she was 7 she had full mastery of the command line and was writing her own bash scripts to provide herself with functionality similar to your "PlayOS".

The other one never got into it, he prefers to use the gui with the touch screen and mostly consumes minecraft or youtube videos about minecraft. If he needs tech support he asks his sister. I'm fine with all of it. He builds some amazing things in minecraft.
Is it really needed today? GitHub can host documentation and releases. GitHub CI is free as well.
Having to piece together a Python installation can be an annoyance for a beginner. I always offer to help them set things up the first time. Since most of my workplace is on Windows, it's easy to have people install WinPython.

This is especially true if they've already tried setting things up, and have made a mess of it. Because WinPython is self contained, it can work on a computer that already has a working or non-working Python installation.
It can get much, much worse. We had a customer that set a net-60, it was the first time we landed an "enterprise" type deal and we sort of missed the net-60 part of the contract (I know, lol). So after 2 weeks we called the customer asking if everything was alright and that we hadn't received the payment yet. He let us know that a net-60 doesn't mean they reserving 60 days to pay, it's that they actually pay after 60 days. Well that blew our minds, but we patiently waited the 60 days.. nothing. So we called to their finance department and we got a callcenter worker in a far away country that actually tried to negotiate a 10% discount on our order for a more speedy payment.

In the end they paid 2 weeks after the net-60 expired. Probably calculated to be maximally annoying with the least amount of risk of legal costs. Really takes the wind out of you. Selling to California startup type companies is so much nicer, I once took a call, negotiated a whole new pricing model closed the deal, entered the product details into FastSpring and the customer paid 40k for the yearly subscription on that model that same afternoon.
Even brick and mortar stores definitely will sell special items (discontinued items, returned items, etc.) on an all sales final basis sometimes.
In this case one doesn’t even need to be a visual person. I can’t even understand what this app does without a screenshot.
I've been using https://github.com/OrJDev/create-jd-app which is based on solid and it's pretty great.

Super fast out of the box, but I also upgraded vite to 4 with a few overrides to get swc.

Solid Auth is still a bit immature (I ended up writing my own Auth stack around prisma, trpc and jwt), haven't tried Next Auth
> The very reason I don't consider Go a language "suitable for beginners" is precisely that its compiler accepts so much code that is very clearly wrong.

This struck me as a really insightful thing to say. I often talk about how I like languages with strong type systems, and how I like using those type systems as fully as my brain thinks is reasonable to do so, because when the compiler finishes with no error, I have much more confidence that what I wrote is correct.

But I never really thought about it from the other side: being beginner friendly doesn't just mean "you can pick up the syntax in an afternoon". It should mean that the compiler saves you from beginner mistakes. As someone who only occasionally uses Go, I'd consider myself an "advanced beginner" at the language. And I remember many of the times I wrote code that seemed correct, and the compiler accepted, but was wrong because of Go's quirks.

That alone is a reason to disqualify Go for me as a language to get serious work done in.
Yes the US has publicly stated they are avoiding delivering weapons which could be used to strike inside Russia.
Parents teach their own niche skills to their children all the time. Which is why for most of history, children entered the field their parents worked in. Cobblers begat cobblers, potters begat potters, etc.
Issue #1 is likely because the "live chat" is a separate product that they bought and linked on the main website, but which is not integrated into the user database or authentication system at all. Therefore the bot needs to ask you for all this identifying information even though you are already logged in.
So, youre asserting that democracy works vest when disfavored minorities are suppressed?

How do you imagine the civil rights movement would have worked out if unfavorable positions of the time were suppressed?

How would that work for LGBQ rights?

There is no value in suppressing bad views. Exposing them let's them be recognized for what they are. Suppressing them causes them to grow and fester in the shadows.

What people really fear is that people will not be intelligent enough to discern these bad opinions, that is an entirely different issue.
I recently discovered it. It's pretty amazing for how incredibly easy it is to build distributed applications with it, that is the part which impressed me the most. It handles concurrency well for sure but same program seamlessly across multiple computers is just awesome. I know it's basically just taking this functionality from being built on top of erlang already but it's still very impressive. Plus like crystal if you already know ruby, having tried to base it's syntax on it, it's an easy thing to pick up if you can grasp the functional aspects too.
What is the NuttX community like compared to Zephyr? Seems like they have similar goals and I noticed that the latter has ten times the number of open pull requests.
Win95 was both, it didn't preempt Win12 apps, they'd all run in the same VM space, but 32bit ones could be preempted, but still take down the system. Full protetion eeded the NT kernel.
This is also why NodeJS got so popular. Concurrent programming is made so damned easy in it, that of course it blew up in popularity.

Most folks just need concurrent code, not parallel code. NodeJS was able to provide that.
Well for code that gets executed billions of times spending more human cycles seems a fair trade off. For boring old corner shop crud, maybe not.
That statement is from a prosecutor, who would have been as generous to the DOJ/FBI as possible in their wording. That it still sounds bad is telling.
This statement feels pithy, but is it actually true?

In order to participate in the US market, you have to comply with US regulations. Sure, morally dubious businesspeople might decide to move their business to some unregulated developing country, but that doesn't get around the fact that their company's products need to comply with US regulations to be sold in the US. As such, stricter product safety regulations aren't going to play a factor in moving operations abroad (though labor costs/practices still might, just as it did before).
> Go has some warts, but they're all things that make sense if you know some basic concepts about go

That's exactly the problem. I don't want to spend my time learning the myriad quirks of a language. I want to spend my time building my program. As someone who is an "advanced beginner" at Go, I assure you that just knowing "some basic concepts" is not enough to avoid Go's pitfalls and footguns.

I don't want to work in a language where the solution to all these things is "just be careful when writing code". I'm fallible. Compilers, less so. The compiler should be doing this work for me.
static would move the construction to before main(). In big projects that becomes an issue, when you have tons of little static objects defined here and there.
But why should the passengers leave? If southwest accepts your money and says board at gate #3, shouldn't they have a staff at gate #3 to handle those passengers?

Being a pain in the ass for the airline seems fair. You wan't the airline to have a same interest in getting you to your destination as you do. Instead of saying "leave the secure area, walk for half an hour, get in line with everyone else that's flying today, and then have fun going through security for the 2nd time".

The idea the gate staff shouldn't manage the the customers sent to the gate seems insane to me.
> the broker could have said “they’ll pay you $x per bag and they need 6,000 units”

That's possible, but unlikely. The whole concept of "bags" just doesn't enter into it in a wholesale transaction.

But even if this did happen, they could have avoided the problem by clarifying: "So that's a total of $X, right?"

Also, at some point this deal should have been put in writing, at which point, again any ambiguity should have been resolved. They had a lawyer, surely they would have asked him to review the deal before signing?

Sorry, but there is just absolutely no way to spin this so that this is not 100% their fault.
It's a little presumptuous to assume the teams and developers using Go are lying to themselves about Go vs. they've made the calculations and like the tradeoffs. Opinionated language and tooling plus good enough performance without a runtime may be worth more to them than the two (?? I lost count trying to find them in the article) issues the author brings up.
No one can make that judgment without seeing the paperwork. We don't know how it was written down.

Also they are a really small business. 6k bags a year, their old volume, is only 23 bags per day (5 days week, 52 weeks)! Of course they were out of their depth, and very naive to how this all works. It's not fair saying they are morons and don't deserve to be in business though.
> We had backend devs doing frontend development with jQuery when we were using Vue. Frontend devs started doing UX design and things looked like trash. QA was done by basically anyone so as you can imagine bugs started appearing everywhere.

Yikes, what a terrible take. To me, "T-shaped" people have at-least-minimal competence across a broad spectrum of the business. They don't do the work of other specialties, but they use their knowledge to avoid making excess work for those other specialties -- for instance, they make better-informed suggestions in brainstorming. Your backend devs know how the frontend stuff works, so they don't make tortuous APIs; they know how QA operates, so they plan for testability; they know the pitfalls of UX so they don't make rigid state-machines that punish users. And, if a disaster strikes and a team needs a helping hand in a pinch, maybe somebody with some depth outside of their role can pitch in. Making everybody do everything always is not T-shaped, it's, I dunno, #-shaped.
I had my inferior turbinates reduced a week ago. Already I am breathing a lot better, and I can feel I'm not fully healed yet (gets better every day). Should have had it done years ago. Something (not sure what) caused the turbinates to become larger some time ago, giving me breathing trouble. It's incredibly liberating to be able to nasally breathe freely again. I might even go so far as to say (utterly unscientifically) that I feel that I'm thinking more clearly now too!
Thaslts the rub. Everyone is the good guy in their own story, right?

People on the whole also have a poor grasp of history and struggle to grasp how different things really were in the past.
Observability is great but it doesn’t give granular enough insights into what is actually happening.

Given a black box you can do two things: watch the black box for a while to see what it does, or take it apart to see how it works.

Observability is the former. Useful in many cases, just not here.

If you want to know what LLMs are actually doing, you’ll need the latter. Looking at weight activations for example, although with billions of parameters that’s infeasible.