skysight-inc/HackerNews huggingface dataset:
There can be several reasons for that. Say your project doesn't only require gradle but other tools to be run too. Or say there are some post-scripts or pre-process-scripts that need to be run. They can be done easily like:

build pre:
! echo 'pre script'

build proj:
! gradle hello

Plus, you might want to run some python scripts or run some other shell commands during or after you have built your gradle project.
> Supposedly the "important" people are still employed.

Karpathy is still on a "sabbatical". The odds of him returning from that is pretty much zero.
Nope - here's the original paper on the algorithm in question: https://arxiv.org/pdf/2110.01111.pdf
No, it's not. Previously discussed on HN here: https://news.ycombinator.com/item?id=28758106 (https://arxiv.org/abs/2110.01111)
To be honest, it would be trivial to wire up a Telegram Bot to read posts that you send it, and to re-post them on a web based blog platform.
I've suggested a shortened edit of the original, if you compare my version to it.
Learn both. Go in particular is quite simple. Rust will take a bit more time.
That document starts with this:

> While Remix can serve as your fullstack application,

Isn't that where most teams should start, and where they should stay unless they have a really good reason to get more complicated? This is what I was thinking of while reading the GP comment about Next.js.
This kind of question is the reason why you'll never be good a good developer

> I am a full stack TypeScript dev looking to broaden my skill set by learning a new language. I’ve been weighing Rust vs Go for a long time but can’t really decide which would be a better use of my time. I often hear that people who try one of these languages after coming from something like TypeScript feel that they really level up their abilities/understanding.

I don't know if that's a joke or just misinformation
If you want to build web services, I'd go with Go. It has an http library in its standard library. It generally has a bigger standard library. Rust has a bigger stdlib than say C++, but it's still pretty anemic by the standards of modern languages. Go also compiles a lot faster than Rust, which is a major point.

If you like functional programming, or want to write embedded software, or high-performance software, I'd go with Rust. All those things are a lot easier in Rust.

Personally, I use Go for scripting and Rust for big projects, because Go compiles fast enough, has a nicer stdlib and dependency management than Python; while for big project my natural tendency to think functionally would make it too annoying having to translate simple concepts into programs twice as long as they need to be, expressing what they're doing very indirectly. But I don't write web services, so that's a different story.
The entire statement is founded on racist reasoning to engender an emotional response. If you're racist tactically, that still means you're racist. Just like the person who was quoted was being.
Plex does music for free, and offline downloads are available if you get Plex Pass (and the lifetime plan is an incredible value)
Where I live, I can try to use 4G. I get one bar of signal and when it's working I get anywhere from 0.2 to 20Mbps with 700ms (!) latency. It costs $80 for 150Gb a month.

Or I can use Starlink. I get a solid reliable signal, anywhere from 20-250 Mbps with 60ms latency. It costs $110 for unlimited bandwidth.

The real competition where I am is fixed wireless. That's 12 Mbps, 70ms latency, and $100/mo.
It's sad that they announced no withdrawals and the Twitter feed is full of people asking if they can transfer to their hardware wallet. What do they think no withdrawals mean?
By that metric Microsoft utterly dominates the web server market.
We lived through a lot of the controversial bullshit tactics of the RIAA. Remember when they sent out requests for DRM settlements en masse, threatening to take people to court if they didn't cough up a few thousand (regardless of whether they actually did download copyright material)?
> Sure, but what if you are just being lazy and you don’t appreciate what it should look like long term?

I wasn't aware that some devs have a side hustle as fortune tellers?

On a more serious note, you should take a look at Sandi Metz's "the wrong abstraction". https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction
I was able to do something similar by myself in only about a month or so (ops and production ready with backups etc) using https://www.digitalocean.com/community/tech_talks/getting-st...

Once you understand the concepts it's not hard to debug. It's fair to acknowledge that kubernetes is complex, but also we should not ignore the real work that has been done in the past few years to make this stuff more accessible to the developers that want to learn it.

Also, saying it's not "alone" in this example I think is not fair. What would you count as "alone"? Setting up the kubernetes cluster from scratch and writing your own helm charts? Using that same logic, I can't say that because someone else designed and built the hardware it's running on. I think it's fair to say that if someone, independent of coaching, regardless of the underlying infrastructure produced some production grade infrastructure by themselves, they certainly did it alone.
For the typical developer familiar with one or more C-style languages (Java, Ruby, JavaScript, Python, C, C++, Go, shell scripts, that kind of thing) and not much more, learning Rust will make you a better programmer, because it makes various kinds of sloppiness harder or impossible and forces you to be more careful about things like shared mutability, in a way that does transfer to your style in other languages, so that you’re much less likely to perpetrate various kinds of errors, among other improvements.

Source: myself and literally every other person that I’ve talked to about the matter.
Why are you asking Hacker News about this and not your daughter? Hacker News doesn't know your daughter.
Well, I'd much rather maintain an application written in Rust or Go, than written in C.

But for gaining understanding, I think because C is so 'raw', I think that makes it useful for developing further understanding as a programmer.
Disclaimer: I have no TypeScript experience. I'd say poking at both languages is useful. The choice of ecosystem can come later, according to the taste and tasks.

Rust:

- makes you a better coder indeed, Rust is pretty clear and organized about its abstractions. Sum types, honest traits, no nil values, disciplined approach to errors and generics, the right amount of niceties and syntax sugar. The idea of borrow checking (and when to avoid it) is a valuable insight into programming in itself. Straightforward RAII instead of wanton `defer`s everywhere.

- fearless concurrency (no global mutable variables, Arc, Send + Sync, ownership of objects by threads) with reliability heads and shoulders higher than everything else.

- first-class support for WebAssembly (wasm-bindgen, js-sys, wasm-pack, etc). Interfaces with other languages well (PyO3, Node bindings, C/C++ via bindgen/cbindgen).

- fine-grained, low-level control over memory allocations and layouts.

- requires quite a bit of effort and dedication to use it effectively. The standard library is extensive in volume (not functionality), takes time to learn, has its own conventions and context-dependent, non-straightforward idioms.

Golang:

- a language to get things done, with very decent and extensive ecosystem.

- a perfect choice for backend servers, microservices, everything working over the network.

- teaches about perils of freely mixing shared memory with concurrency. Goroutines are so easy to spawn, until they are not. Channels seem like a good idea, until dive into a real code base with mutexes and shared memory. Still, both goroutines and channels are solid, practical tools that work well.

- writing new code is objectively faster and easier with GC.

- compared to TypeScript, still teaches to manage memory layouts and has structs as values.

- doing pretty basic things like iterators, sum types, custom data structures, even tuples of values can be painful, but this is changing with the newly introduced generics.

- I still try to come to terms with the wild abuse of programming language theory terms in Go, where an "interface" is not just a trait, but also a set of types and behaves almost like a supertype.
Very nice. Can this be applied to more than 4 dimensions?

This problem is an abstract of a network firewall rule optimization. The a,b,c... are for source IP/net, destination IP/net, protocol/port, permit/deny and probably more like zone names.
I'd choose goth/rock/techno/industrial-metal and stuff from the 80s. She'd choose goth/rock/techno/90s music.

So a reasonably high amount of overlap, which is why it's a bit fascinating.

(I guess I learned early on that he liked loud drums, loud rhythms, and repetition. Things like Rammstein - Fier Fier, Prodigy - Firestarter, so I tend to bias myself in that direction if he's nearby or listening with me. Maybe that's all it is, but it's fun to observe.)
Try both and pick the one you like the most
>There are plenty of ways. ... have those devices film the user.

I think you've identified pretty much the only way (that I can think of, anyway). If you surveil all consumers and instantly arrest them the moment they make a copy, mission accomplished.

Short of that, though, as long as the data is being presented out in the open (light waves, sound waves, text), it's going to be possible to "rip" it.
Wow, this is easily t he creepiest comment in HN history.
Success is rarely so rapid that you can't throw money at a problem temporarily and build something more robust.

No one is advocating for a single server running in your closet, but a large and well funded PaaS can handle any realistic amount of growth at least temporarily, and something like Heroku is big enough (and more importantly, owned by a company big enough) that shutting down without notice is not a possibility worth considering.
Untrue. Editing titles is specifically permitted to improve the title quality:

If the title contains a gratuitous number or number + adjective, we'd appreciate it if you'd crop it. E.g. translate "10 Ways To Do X" to "How To Do X," and "14 Amazing Ys" to "Ys." Exception: when the number is meaningful, e.g. "The 5 Platonic Solids."

Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize.

https://news.ycombinator.com/newsguidelines.html

And shortening is specifically permitted as well:

https://news.ycombinator.com/item?id=21515548

https://news.ycombinator.com/item?id=31962722

https://news.ycombinator.com/item?id=31743041
https://drawbattle.io/AMHQ
And a "€5 per month after 12 months of inactivity" fee too I see!
Sounds more like a parasite.
Adding for context: I don’t have a degree/background in CS. I majored in Math back in college and learned Python followed by a js bootcamp. I’m now years beyond that and have developed what I’d deem is enough of an understanding of CS fundamentals to the point that I can comfortably speak about/implement most things in the leetcode/technical interview space.

My college didn’t have cs and I definitely feel like I missed out on learning about some really interesting things and now have an understanding that can only go so deep across the stack.

Based on this, let me know if you think rust is the better choice, or if you have any other thoughts as to how might be good to spend my time e.g. maybe I’m just in the wrong space entirely and should be reading a book on Postgres… I love learning new stuff, but I sometimes find that I don’t invest my time in the wisest thing at a given moment. After thinking on the replies, I am now supplementing this post with a request for whatever you think would help someone like me
Capitalism existed for centuries before the McKinsey, which is an outgrowth of the 20th century movement of “scientific management.”
I will take a crack at this...

> where free and fair elections, along with human rights, are being turned down this year

Pure, uncut, refined hysterical hyperbolic nonsense
I used it every day and it does almost all of my daily driving. If it never improves from where it is now, it will be worth the $6k I paid for it.

And yeah, you gotta watch it and pay attention.
It is almost like there is a reason and purpose for having highly regulated financial markets. Who knew?

At least when Full Tilt Poker was raided the previous decade the online gamblers didn't pretend Full Tilt was some kind of depository bank.
I’ve run DevOps and know from experience the pitfalls. I’m sorry that you’ve interpreted my general agreement and elaboration of your comment as nitpicking foolishness.
That is an interesting point - though no other devices are affected so it is unlikely that this is related to power.
Robertson screws were legion in the Mobile home industry in the 80s and 90s. Also saw them in some "not user serviceable" electronics where they were an early nod to what we'd call security screws today.
Your partner is going to need support even if she isn't pushing for it and all seems well, if she's up all night at intervals feeding but you're sleeping well, eventually it becomes irritating. Be willing to do expressed milk or formula feeds in the night, deal with nappies / diapers willingly, make some time off for her by taking the baby out for long walks or car trips when it won't fall asleep etc.

It varies but doesn't be surprised if you don't really feel much about the new arrival until after a few months when it becomes clear there is actually a person in there. It doesn't mean there's something wrong with you.
This is actually the default result you get if you leave the defaults alone in some CI systems! My current company runs CI this way, in fact. A checkout is re-used between builds, and Gradle computes the minimal set of tasks that need to be run based on changed files just as it would locally. TeamCity will set things up this way by default. If you want a clean build on every run, you have to opt-in by checking a box.

How well does it work? Well .... it sorta mostly works. Sometimes a build will fail for inexplicable reasons because Gradle/Kotlin incremental builds don't seem fully reliable. You re-run with a clean checkout and the issue goes away.

How much time does it save? Also hard to say. Most of the time goes into integration tests that by their nature are invalidated by more or less any change in the codebase. That's not exactly incorrect. Some changes in some modules do avoid hitting the integration tests, though.

TC can also do test sharding in the newest versions when you use JUnit. We don't use this yet though.
Very good tips, thank you!
Those remakes are exactly why it shouldn't last much longer. As those remakes aren't actually about the work itself, but about the brand recognition that work has in the public consciousness. It's just free advertisement that you don't get with an original work, which is why remakes and sequels are so popular, even if the connection to the original is little more than the title.

It's not the job of copyright to allow people to get lazy or companies profiting forever from the rights they bought. The goal should be to encourage original works and current copyright isn't very good at doing so.

Also it's not like the author would go completely penniless here. Just because everybody can make a StarWars doesn't mean there won't still be a George Lucas approved canon-StarWars. Slapping the authors name on your product to declare it the "Read Thing™" might still be worth a bit and might frankly be better than today's sequels that happen completely without any of the original creators being involved.
I don't think Go or Rust provides anything similar to what you have in Erlang/Elixir. I've done a lot of Ruby and then while learning Haskell and Elm has been a paradigm change with their type systems, Elixir/Erlang felt like a much bigger step in terms of a different required way of approaching problems.

It's not that it's functional (that's completely secondary in Erlang) but its fault tolerance primitives (processes, pids, mailboxes, monitors and links) and the OTP abstractions (GenServers, Supervisors, etc).

You learn to think in terms of distributed systems and think about fault tolerance in a way you cannot in other languages as they don't provide the primitives. It's quite a big leap and it takes time to sink in.
I've used both for a couple of projects, but my primary language of choice for most things nowadays is Rust so this will be a bit biased. However, Go is a fun language to use, it is incredibly easy to get up and running, it provides most of the tooling you need in a language (formatting, testing, linting etc) and compiles very fast (especially compared to Rust). It is a simpler language than Rust, and is missing a fair bit of more advanced features that other new languages has. Coming from TypeScript, I suspect Go will feel like a simpler version of it, the generic programming and type level magic you can do in TypeScript is far more advanced than the generics that Go (finally) has.

Comparing this to Rust however is a different ball game, where Go is straight forward and fairly easy to use, with Rust it can feel like the compiler is your enemy. Learning how the borrow checker works, why there are a whole bunch of string types, how mutability and references work when passing them around and so on is a serious undertaking. But once you get somewhat comfortable with it Rust is great. The compiler will guide you along with very helpful error messages, you can use pattern matching, traits and a advanced type system to your advantage to build very performant and easy to maintain programs.

In terms of getting "to the next level", I would highly recommend trying out Rust. Go is not a language that will challenge you the same way learning Rust will, the concepts and patterns from other languages map over fairly well to it (though the concurrency story in Go is really cool, definitely give it a good look!) whereas Rust will be more foreign.

I had used Rust for a few years when I worked on a couple of programs written in Go and it took me a week or two before I felt mostly comfortable with it. With Rust however it took me a few months to stop getting compiler errors every time I saved, and a few more months to internalize why the borrow checker complains. But working on the projects using Go felt like a downgrade from Rust, I gotta be honest. So many times I sat there thinking about how features from Rust would've made things so much neater... though now I feel the same with Haskell and Rust.
Though many cities have them they're sort of glossed over in drivers ed and it clearly shows at times.
Wait, aren't Stax the electrostatic high-voltage headphones? I think at that point, "Convenience" is deeply crossed out as a selection criteria, and a portable phone while jogging is not a likely scenario :).
It feels similar at first blush but it's not really. In bubble sort you compare/swap adjacent elements, and exit if you make a pass through the collection without making any changes. Whereas this will compare/swap the element at every index to every other index, and just exits when it's done performing all those comparisons.
Good recommendations in the thread.

I would ask myself: what would I expect to be building with Go or Rust? Of course, you can build anything with Go or Rust --or any turing-complete programming language for that matter. But *I believe* Rust programmers will be working mostly on foundational software --think caches, databases, compilers... while Go developers will mostly work building microservices and related tooling, stuff a little more business oriented.
Learn go. It’s much more widely adopted with very significant open source projects written with it.

You will become productive very quickly and it will help you make better use of multi core processors.

Go just introduced generics which was holding back quite a few people from trying it. Now it’s the time.
Did you watch the video? There's absolutely nothing confusing about the tram coming towards the Tesla, whether it has the right-of-way or not. And there's nothing in the video that suggests the tram was running a red light.
Thanks for forwarding my comment, it's much appreciated! I opened a ticket a while ago ago, I'll add this comment to the conversation. We're working on setting up our runners in the meantime.
From the article their roll was aes cbc which in itself is perfectly fine…but they did hmac it
Try taking her to a local library and asking the librarian in the children's section. Libraries often have fun and educational activities for children and families to enjoy. If they don't, at the very least the librarian should be able to help you find books of projects for kids to do.
> Practically, you do at some point in the chain.

Except you don't - they can be sold and bought entirely without a digital middleman. You can buy goods for them. It's not a weird thought to keep them entirely as themselves, forever.

As for the "crypto is very traceable" angle, it's honestly kind of tired and wrong. If it's something you care about, you have solutions available. Arguing about it as if it's some sort of absolute is disingenuous.
I have a Thinkpad X1 Extreme Gen 2 with i7 processor and NVIDIA Max-Q graphics so I think the issues common on low-end machines are unlikely to apply in this case.
> But the next advice about not using a different language for frontend and backend is wrong.

Er.

I read this as him saying "one of the things I've seen as a bad reason to use Kubernetes is that there are multiple languages in use."

I've seen people do this. Frontend in one container, backend in another, Kube to manage it.

If that's what author meant, author is right, that's a profoundly stupid (and common) reason to involve Kube.
Doing a few projects in Go will make you a better programmer in general, a it forces you to write simpler, more comprehendible code.
Do people really need a lesson to know not to turn just in front of a tram?
How is it faster? And faster at what?
I don't know where you lives, but do hicking with her if you have time.

Try to do some theater of mind games (d&d or whatever she or both likes). Maybe you can't afford going somewhere but nothings tie you there.

Talking about that if you lives in a city big enough, there must to be hidden places with a story to tell, grab a map a visit that with her. Think about a story you can tell with that. I learnt more about buenos aires (the city where I live) and Chicago (the city where I'm moving soon) because Dresden Files books and roleplaying, than from school. And I learned how to love every city secret because of that.

Why I'm talking about roleplaying and walking time together? Because both will be spending time together and will be knowing (a looot) each other, and over that, you will be feeding her imagination and curiosity.

And it is free.
>BSD was used by apple to build a massive fortune but without paying significantly back to the BSD community.

Welcome to free software. :)

If you had to "pay back significantly" to use it, it would not be "free software".

It's regrettable, but it's the price of freedom. Whether that's worth it is subjective. Stallman's answer to this was the GPL. (I bet Apple wouldn't've touched BSD if it was GPL'd.) Newer, hybrid license have also emerged (like the MPL) that attempt to strike a better balance between freedom and back-contributions.
Basically none of that needs, or is helped by, kube
I'm not against new tools, we should absolutely embrace innovation. But show me how it's better, don't just make some claims with no evidence and expect me to buy into it.
Deepnote (YC S19) is working on this (I'm the founder).

https://deepnote.com/
I really don't understand how Tesla markets something as "Autopilot" and "Full Self-Driving" and then also says "oh it's beta" and "you must be ready to take control of the car at any second".
Untrue, most of the weebs I ever met were obsessed with kansai-ben and were all about "Osaka" life.

There are all kinds of weebs, and it's not limited to Tokyo.