pornel

48 ms·

781.
by pornel 2y ago
There are off-the-shelf standard components for all major parts of the EV drivetrain. The custom work is mostly in wiring that up, and building a battery cradle and motor mounts that can be installed without compromising car's original
782.
by pornel 2y ago
There are regular "battery breakthrough" announcements, but if they ever leave the lab, they end up being incremental improvements. This one sounds like it exists in a form that can power an actual car, but I'll reserve excit
783.
by pornel 2y ago
Telling time, showing notifications, and tracking sleep is 99% of what I need the Watch to do, and Pebble could do that with a week-long battery life.
784.
by pornel 2y ago
Rust projects are pretty easy to deploy. It's just LLVM underneath, and the product is similar to clang-built code. You get a library, static or dynamic, that you can link with anything that can link with C. Rust projects are much easi
785.
by pornel 2y ago
That live reload probably already works with Rust — they say they don't parse any source code, and instead analyze the compiled binary and debug info.
786.
by pornel 2y ago
Because in ASCII it also plays a role of the left single quote, so you get a geometric compromise.
787.
by pornel 2y ago
1. You dynamically add components to any entity, so entities don't have a static type. Semantically they're comparable to a JavaScript Object where you can add and remove properties at will, rather than being structs or class inst
788.
by pornel 2y ago
C++ will easily let you write non-thread-safe code anywhere, won't complain about multiple mutable pointers to the same object, will let you leave pointers dangling and resources leaked. Such code is of course crappy, but the OP wants
789.
by pornel 2y ago
ECS is like a whole another language on top of Rust, and it is dynamically typed. If you add a scripting language and blueprints, you're shortening the feedback cycles by using Rust less. I like Bevy, but it seems like Rust currently
790.
by pornel 2y ago
They've given out a bot identification signal. Now botters are going to deliberately cancel 6% of their TCP connections ;)
791.
by pornel 2y ago
Unicode is not that semantic. It inherited ASCII (with no minus) and a ton of presentational (mis)uses of code points. It's so messy that Unicode discourages use of APOSTROPHE for apostrophes, and instead recommends using RIGHT SINGLE
792.
by pornel 2y ago
The author has one major issue with Rust in gamedev: they can't easily try out new game feature ideas or gameplay tweaks by writing quick and dirty code. Such unfinished code can be obviously buggy and unsafe, but in game dev it matter
793.
by pornel 2y ago
H/2 doesn't solve blocking it on the TCP level, but it solved another kind of blocking on the protocol level by having multiplexing. H/1 pipelining was unusable, so H/1 had to wait for a response before sending the next
794.
by pornel 2y ago
Why would chargers break compatibility? The protocols are open standards, and there's a huge install base for them in both cars and dispensers. Even Tesla's NACS adopted the ISO 15118 protocol, the same as in CCS cars in US and Eu
795.
by pornel 2y ago
Modern gas cars have all the same touchscreens, with the same software, and the same apps talking to the same servers. EVs are equated with being computers on wheels, but that's just because barely any BEVs existed in the pre-software
796.
by pornel 2y ago
Whenever WebP gives you file size savings bigger than 15%-20% compared to a JPEG, the savings are coming from quality degradation, not from improved compression. If you compress and optimize JPEG well, it shouldn't be far behind WebP.
797.
by pornel 2y ago
Productivity tanks only temporarily. I know that writing your first 10 lines of Rust code will give you 15 novel compile errors, and that feels like it's impossible to get anything done in Rust, but once you get over the hump, you get
798.
by pornel 2y ago
Rust superficially looks like C++ to avoid looking weird to existing C/C++ programmers, but semantically it's quite far from C++. Rust's generics are not like C++ templates: they're only type based, and don't use sy
799.
by pornel 2y ago
TIOBE index is a horoscope for programmers — it's useless junk, and you can only use it to reinforce your pre-existing beliefs. TIOBE has shown that beteen 2016 and 2017 the C language has dropped by 50%, and then in 2018 it miraculous
800.
by pornel 2y ago
Cloudflare serves ~20% of the Web traffic, and several critical components on the request path are written in Rust (proxies, caches, firewalls, compression, some encryption, etc.) At Cloudflare Rust is de-facto the default language for new
801.
by pornel 2y ago
This has stopped working many years ago. Every top-level domain now has its own private cache of all other domains . You likely have dozens of copies of Google Fonts, each in a separate silo, with absolutely zero reuse between websites. Th
802.
by pornel 2y ago
They're using "no_std" Rust, which is quite bare-bones. Usually the standard library adds 300KB+, but without it it's just cost of the code you add. With a little care, you can get the same code size as you'd get in
803.
by pornel 2y ago
What has Tesla contributed here? The train looks like an existing battery-powered Siemens Mireo: https://en.wikipedia.org/wiki/Siemens_Mireo#Mireo_Plus_B
804.
by pornel 2y ago
Rust is its own thing, but use of algebraic data types + pattern matching and type inference makes it feel closer to OCaml than C++. The original Rust compiler has been written in OCaml, so that's definitely an influence.
805.
by pornel 2y ago
You can get some of this speed back with HTTP/3 0-RTT start, and use 103 Early Hints to make browsers preload assets early. This combo has an advantage of being semantically backwards-compatible with HTTP/1 (reverse proxies, load
806.
by pornel 2y ago
Rust is much better suited to static analysis and formal verification than C++, primarily thanks to stricter pointer aliasing, immutability without loopholes of const, and thread safety annotations in the type system. Most things that are a
807.
by pornel 2y ago
It's sufficient. Another implementation is still unlikely to have the exact same bugs. Especially rewrite in Rust will force the code to be structured differently (Rust is very opinionated about that). The spec is big enough that the t
808.
by pornel 2y ago
I think it would make more sense to support the existing implementation than to start yet another one. As for why jxl-oxide can't be used yet — it just isn't mature enough yet. They're still finding unimplemented or incompati
809.
by pornel 2y ago
This is a great news for JPEG XL. Web standards need two independent implementations of every feature – this proves that the spec is actually possible to implement, and makes it possible to verify that the implementations are interoperable.
810.
by pornel 2y ago
crates.io sees about 13% of requests from nightly compilers, although that may be biased by CI tests that just check for future compatibility rather than needing nightly features. https://lib.rs/stats#rustc-usage For appli

More ›