Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jfkebwjsbx
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
91.
▲
by
jfkebwjsbx
6y ago
We were talking about the borrow checker and memory safety, not about memory limits, access patterns, etc.
92.
▲
by
jfkebwjsbx
6y ago
Please read the context. We were discussing the borrow checker and memory management, not other features. Regardless, there are other languages with better type systems and functional features.
93.
▲
by
jfkebwjsbx
6y ago
Dynamic linking has been a thing for 50 years. No need for WASM for that.
94.
▲
by
jfkebwjsbx
6y ago
You were talking about the borrow checker, which is mainly about memory safety, not memory limit issues. In Python, C#, Java, JS... you are memory safe without dealing with memory management nor a borrow checker. There are many languages ru
95.
▲
by
jfkebwjsbx
6y ago
The borrow checker only checks, it does not solve the problem. In other languages the problem does not even exist to begin with. It is not a trivial problem to solve (as you claim), otherwise we would have never needed the borrow checker
96.
▲
by
jfkebwjsbx
6y ago
People is downvoting you, but you are correct. Rust is ideal for CPU-bound problems were performance is critical. For typical web services, not so much. It is hard to justify the extra development cost, even if hiring were easy (which it is
97.
▲
by
jfkebwjsbx
6y ago
All that applies to several other very mature languages that can target WASM, like C. Nevertheless, WASM is not ideal for server work. It is intended for the frontend.
98.
▲
by
jfkebwjsbx
6y ago
Having to care for memory management is by definition very low level.
99.
▲
by
jfkebwjsbx
6y ago
Cargo check does not help with what the parent is talking about, which is a edit-compile-run loop.
100.
▲
by
jfkebwjsbx
6y ago
> No process nor code is trusted in my company. Then you cannot use any modern computer in your company. Much less hypercomplex systems like Node, v8 and JITs in general. > compared to the multi-million risks What "risks"? W
101.
▲
by
jfkebwjsbx
6y ago
No, it is not a good idea for backend where your processes and code are trusted because it does not come for free (it comes with a big performance penalty). Mixing languages does not require WASM in native code either. It has always been do
102.
▲
by
jfkebwjsbx
6y ago
It is not. A very useful function does not mean you have to use it in the hot path or for huge inputs.
103.
▲
by
jfkebwjsbx
6y ago
Good points, but when I have done that, I always preferred to start fresh, rather than take a "shortcut" map from A to B. The reason is that otherwise you always try to map things back to your previous knowledge and expertise, whi
104.
▲
by
jfkebwjsbx
6y ago
If they wanted something better for the backend (for robustness of performance reasons) there are other alternatives much better suited for the vast majority of backends. For instance, C#. WASM is not needed for the backend, so that is not
105.
▲
by
jfkebwjsbx
6y ago
The question is whether enough people need such a map.
106.
▲
by
jfkebwjsbx
6y ago
Not really. Many other mainstream languages give you memory safety, strict type systems and overall robustness without having to deal with memory management or low-level details. Even for parallelism this holds true. I would say it is even
107.
▲
by
jfkebwjsbx
6y ago
JavaScript and Rust are so opposite in their goals and design that I wonder why something like this is written...
108.
▲
by
jfkebwjsbx
6y ago
Rust (and others like D, Ada, Zig...) won't be ubiquitous because it is a systems programming language intended to replace C and C++. This kind of languages are specialized and more costly to develop in them. Everything else (the world
109.
▲
by
jfkebwjsbx
6y ago
CPUs does not win in smaller datasets but in small computations.
110.
▲
by
jfkebwjsbx
6y ago
> Some of the very brightest software engineers in the world work at Facebook Like they work in many other companies. In any case, this is not about being bright but about being diligent.
111.
▲
by
jfkebwjsbx
6y ago
> A) the programmers that made this mistake probably have the knowledge to pass any certification exam you can throw at them Very unlikely. You probably don't realize how tough some professional exams are in some fields. We are talk
112.
▲
by
jfkebwjsbx
6y ago
Safari lacks quite some web specs, so it may just work fine in the rest of browsers.
113.
▲
by
jfkebwjsbx
6y ago
The very definition of MVP means a viable product. It has nothing to do with an "hypothesis". Sorry, but you are misusing the term.
114.
▲
by
jfkebwjsbx
6y ago
The commit is the reason behind a change, not the reason why some code is written like that.
115.
▲
by
jfkebwjsbx
6y ago
No, that is if you want runtime support, etc. If you just want to run some computational code (which is the case for most of the Wasm use today), it will Just Work, as you say. In fact, that is how I sped up a webpage: I just wrote myself
116.
▲
by
jfkebwjsbx
6y ago
And yet they had bugs and could lose data. Which shows 100% unit test coverage is not better than spending that time in other kinds of tests.
117.
▲
by
jfkebwjsbx
6y ago
> - In your average Rust project, all dependencies are already built from source That is only the case for open source code like crates.io, there is nothing that guarantees you will get the source code of a third-party, though. I mention
118.
▲
by
jfkebwjsbx
6y ago
Reference-counted graphs are usually quite fine.
119.
▲
by
jfkebwjsbx
6y ago
Well, you can compile the .NET runtime into Wasm, send it to the client and run C# on top of it, but then you are adding yet another layer.
120.
▲
by
jfkebwjsbx
6y ago
On that front, I agree. Wasm is being sold as the greatest innovation ever, when it is just another virtual ISA with lacking features and performance.
More ›