Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
linkdd
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
49 ms
·
751.
▲
by
linkdd
5y ago
Template errors with g++ vs clang++ are what made me abandon the gcc toolchain for my dev environment (I still build against both compilers in my CI/CD though). Rust wasn't even a thing (not as hype and mature) at that time. Rust
752.
▲
by
linkdd
5y ago
`every()` returns true if every item in a collection verify a predicate (this is the `foldl1 (||)` part of the example). `map()` applies a function to every item in a collection and returns a new collection. What I confuses me about the Has
753.
▲
by
linkdd
5y ago
Haskell is nice, it's type systems allows the developer to prove the properties of their algorithm. But it's so hard to read when you're not used to the syntax, compare this to a Javascript/Typescript solution: const
754.
▲
by
linkdd
5y ago
> simple unit tests aren't the important ones And yet, they prevented me from committing dumb mistakes to the main branch so many times. > types are just simple unit tests written for you Even better if I don't have to write
755.
▲
by
linkdd
5y ago
This is exactly why it's a hard question to answer. Innovation is not always "new problems to solve", but more often "new clever ways to solve a problem", which rules out number 2 IMHO. For example, Kubernetes was a
756.
▲
by
linkdd
5y ago
Same except I don't bin it, I put it in the "projects for fun" box. NB: "What's the competition" is a very hard question when you're trying to innovate.
757.
▲
by
linkdd
5y ago
Was looking for a tool like this, thanks!
758.
▲
by
linkdd
5y ago
Thanks for the insight! Didn't know strum. But yeah, I tend to do more work at runtime than compile-time, which is not really the way to go in Rust.
759.
▲
by
linkdd
5y ago
Yep, I'm still new to serde and the Deserialize workflow :) I come from highly dynamic languages, and even when I was doing C/C++ 10 years ago, I would do more at runtime that what could be considered "best practice".
760.
▲
by
linkdd
5y ago
I stayed on WSL1 for the shared localhost. And WSL2 still have some performance issues related to memory usage and Disk IO. But yeah, I agree, Windows 10 has a great UX. I switched to windows because of the WSL, and I end up using it less a
761.
▲
by
linkdd
5y ago
> for `helloworld` projects maybe, yeah, have you worked on a large Rust project? No need to be condescending... Yes as a matter of fact, I have. Never ran into any problem with "cargo" nor "rustup". > have you tri
762.
▲
by
linkdd
5y ago
What about user-supplied JSON schemas? You can't add types at runtime. Also, JSON schemas allows you to encode semantics about the value not only their types: {"type": "string", "format": "url&quo
763.
▲
by
linkdd
5y ago
Git Bash integrated in VS Code works very well. For Rust/Go/Python/Javascript development, I've never had to rely on any workaround.
764.
▲
by
linkdd
5y ago
Never had any problems with updates (and my work computer has no graphic card except for the integrated chipset in the CPU). > Generally, Windows 10 seems to take control of configuring the operating system away from the user That's
765.
▲
by
linkdd
5y ago
I filter outgoing traffic on my router.
766.
▲
by
linkdd
5y ago
Of course, but what's the point? I use WSL for 3-4 programs, that's it. My entire toolchain is Windows-compatible, and installed through chocolatey with the default configuration.
767.
▲
by
linkdd
5y ago
But the Rust type system cannot fully express a JSON Schema: { "type": "object", "oneOf": [{ "required": ["kind", "foobar"], "properties": {
768.
▲
by
linkdd
5y ago
*any UNIX-like distro Unfortunately, Windows support is not there yet (or am I wrong?). I stopped using Linux as my main distro. I was tired of maintaining my OS with the only argument "but I can do whatever I want", and I've
769.
▲
by
linkdd
5y ago
Rust syntax is weird. Weirdly good and sometimes bad. I'm currently designing my own toy language and writing the compiler (to LLVM IR) in Rust. Representing the AST with Rust's sum types is so simple. Visiting that AST through pa
770.
▲
by
linkdd
5y ago
Function calls to another module ALWAYS introduce a breakpoint so the BEAM (Erlang VM) can check if the target module is up-to-date, and perform hot code reloading if it isn't. Therefore, every function is interruptible (implicit async
771.
▲
by
linkdd
5y ago
> Actually the entire Erlang runtime is "async" I wasn't sure so I did not want to claim it, so thanks :) > async/await being implemented and popularized as it is today everywhere might just be our generations null
772.
▲
by
linkdd
5y ago
Thank you for the clarification. But still, since it's all about composition, the simplicity is a direct consequence IMHO.
773.
▲
by
linkdd
5y ago
> I might describe it as “pathologically easy” to compose functions in Haskell Maybe because "composing functions" is the whole point of category theory, monads and Haskell?
774.
▲
by
linkdd
5y ago
This. The main selling point for me was the "zoom in/out" aspect. Instead of having a HUGE UML diagram, you have a bunch of small diagrams, each focused on a single part of the described system and the interactions between it
775.
▲
by
linkdd
5y ago
In Erlang/Elixir, every function from another module is async by design, and the await is implicit. This is by design to allow for hot code reloading. This is a very sound design choice because true concurrency is achieved through the
776.
▲
by
linkdd
5y ago
No cowboy would treat their servers like cattle. Joke aside, the Linux kernel is mainly developed in C and runs in production everywhere.
777.
▲
by
linkdd
5y ago
> If you had the same reflex with other languages I do, always, just out of curiosity because seeing peoples view on different languages is always insightful. > This isn't specific to Rust in any ways. From what I've seen, R
778.
▲
by
linkdd
5y ago
> Rust has a planned keyword for this exact feature, namely 'become'. So the author would be able to use it in Rust just as well, as soon as support for it lands in an upstream LLVM release. The author is demonstrating a new Cl
779.
▲
by
linkdd
5y ago
Every single time there is a link about C/C++, I do a quick "Ctrl+F Rust", and every single time there is some rant about "but Rust is safer than C". Every. Single. Time. This article is about a new Clang extension:
780.
▲
by
linkdd
6y ago
Inseparable friends they were
More ›