Depending on your needs (i.e. how you would otherwise use your output jspn), using the reviver can have a significant impact on performance. JSON.parse itself is hyper-optimized. At the company I work we used the reviver for almost exactly this, but profiling showed that using the reviver had enormous impact on performance. We cut it out, and won in the seconds of performance for some large json's.
For the parent there's immaterial value knowing that is written by a human. From what I read in your comment, you see code more as a means to an end. I think I understand where the parent is coming from. Writing code myself, and accomplishing what I set out to build sometimes feels like a form of art, and knowing that I build it, gives me a sense of accomplishment. And gives me energy. Writing code solely as a means to an end, or letting it be generated by some model, doesn't give that same energy.
This thinking has nothing to do with not caring about being a good teammate or the business. I've no idea why you put that on the same pile.
I think that DDG's search resulrs worsened from the moment they've dropped the Yandex index, a few years back.
That, and they seem to havr focussed more on localized results, which makes searches related to software development worse. This is also a problem with Google's search engine, but it's much harder to work around on Google.
My understanding is that this only gives you access to C++ TurboModules? Binding to C++ is already easy in Rust (and odten Rust itself is a better choice for these "cross-platform business logic" kind of modules anyway). The value here is in unlocking bindings to the native platform APIs (which are mostly Java/Kotlin/Objc/Swift)
> Waning reliability is but one of many problems for state-owned Deutsche Bahn, which is operating at a loss and regularly subjects its passengers to poor or no Wi-Fi access, seat reservation mix-ups, missing train cars and "technical problems" — a catch-all reason commonly cited by conductors over the train intercom.
As someone who fairly often travels by German ICE (not their regional trains), I've only ever experienced the timetable unreliability.
WiFi is fairly reliable and much much better than for example the Dutch railway (NS) WiFi which never seems to work, and I can't remember the last time it didn't work on an ICE. I've never had any seat reservation mix ups or (knowingly) missing train cars; the last two I've experienced only once in Europe, on a cross border train from Slovenia to Austria, with the seat booked via the ÖBB on a Slovenian train.
When these ICE's are on time and show up, I like them a lot. The seats are very comfortable, there's food service in the train, the seat reservations aren't thát high, and are optional (unlike say high speed rail in Italy, where there's a 15 euro required seat reservation on top of the ticket price), the staff is consistently friendly and so far (I think) they haven't joined the annoying recent trend to put digital ads on the same monitor as the in train timetable.
More so, I really really like the Deutsche Bahn app and use it for trains all over Europe.
Reading this article makes me ask myself if the route and type of train matters, but also that the article didn't really add anything new from what wasn't already known. With their ongoing frequent delays DB made them an easy target for anything under the sun, but comparatively to other trains in Europe, at least for DB ICE's, delays aside, I feel they're doing quite alright.
As an occasional ICE traveler, I can confirm the Wifi, I'm at the point where I don't even bother logging on to the free wifi but just use my phone hotspot. I'd guess it's dependent on the route; Berlin-Munich definitely has dropouts.
This actually seems to use the encoder/decoder from the Rust image crate (1), which would bring the opportunity for more memory safe formats once BMP would be accepted.
I was quite confused too. I thought these were Pikaday implementations, partly because I usually use UK language in browsers, and then you get exclusively these (annoying to me) AM/PM date input pickers, and this time I didn't.
I tried some of the inputs and found that they worked well for initial input, but editing inputs didn't (e.g. the masked date input cursor just jumps over previous decimals, when typing a new number)
I made a reproduction video and tried to report it to the Pikaday issue tracker after which I found out it's deprecated.
Going back, and comparing the readme with the page, does show that the post uses native inputs. ... I feel that could have been more explicit; in this post I expected Pikaday to have the option to use native pickers with some component styling.
It seems to work decently even with just one or two titles for popular titles, but less so for the niche.
For example, the title "Impro: Improvisation and the Theatre" by Keith Johnstone, linked by another article posted to HN today gives back the following suggestions:
- Truth in Comedy: The Manual of Improvisation by Charna Halpern
- Steve Jobs by Walter Isaacson
- 1984 by George Orwell
- Harry Potter and the Sorcerer's Stone (Harry Potter, #1) by J.K. Rowling
- Sapiens: A Brief History of Humankind by Yuval Noah Harari
- The Alchemist by Paulo Coelho
- The Tipping Point: How Little Things Can Make a Big Difference by Malcolm Gladwell
- Dune (Dune, #1) by Frank Herbert
It's a bit unfortunate that all suggestions are fairly popular titles, which are fairly easy to find, while the unpopular or niche may be just as well written but a lot harder to find.
Within niche topics or books, it is also usually harder to provide multiple similar enough titles up front.
It's recommended that you put at least 3 books in. If you would like recommendations just based on one book, click the similar button on the book, it should take you to this page: https://book.sv/similar?id=297914
It's not just people calling, although that's often the case, it's also people just watching social media videos on speaker
reply