146 karma · joined September 24, 2017
A slider to do a bit of time-travelling if possible would be also a nice to have
This is something that feels alien in SF people. A fundamental difference for example from Greece and people living in SF is this.
- Greek opening question: "Which city are you from?" - SF opening question: "Which company do you work for?"
My verdict is that Project Hail Mary was way much more engaging in terms of story-telling. The concepts were cool, and tbh I look forward for the movie and see if the adaptation will be nice
They excel in their respective areas based on the architectural decisions they've made for the use cases they wanted to optimize for.
PlanetScale, with their latest Metal introduction, optimized for super low latency (they act like they've reinvented the wheel, lol), but they clearly have something in mind going in this direction.
Neon offers many managed features for serverless PostgreSQL that were missing in the market, like instant branching, and with auto-scaling, you may perform better with variable workloads. From their perspective, they wanted to serve other use cases.
There's no reason to always compare apples to oranges, and no reason to hate one another when everyone is pushing the managed database industry forward.
Of course an increase in both is the optimal, but a small sacrifice in performance/accuracy for being 200% faster is worth noting. Around 10% drop in accuracy for 200% speed-up, some would take it!
I have no clue
In Europe we even assigned our first "Chief Heat Officer", which makes total sense.
Does that mean there could be cases with less quality in terms of tokenization?
Built in Rust(tauri), GoLang TypeScript and Livekit as WebRTC infra
For the performance critical part, which is the screen-sharing and remote control, everything is done from Rust which is low level and gets the job done.
Native UI in this case wouldn't offer us much more. There is a case that maybe it could be faster in the video rendering in comparison from the browser's <video> tag, but we have not make any tests yet, maybe we should test this in the future.
We chose to go native with Rust instead of just using the screen-sharing provided from Webkit for a few reasons: 1. Granular access to OS APIs. For example on MacOS you can select applications that you want to exclude from screen-sharing, which we know we want to use in the future. https://developer.apple.com/documentation/screencapturekit/c... 2. Being able to tweak the WebRTC client. In our case we patch libwebrtc for minor bugs, and tweak parameters to allow lower latency in video streaming 3. This: https://github.com/tauri-apps/wry/issues/85
Most posts online focus on HTTP servers and though it might be useful to some
After interviewing over 100 so-called “Senior” devs, I’ve found that too many struggle with basic concepts like closures, array methods, and loops. If you can’t explain why your JavaScript code works (or doesn’t), are you really a Senior Developer? What's your take and easy way to filter them out before reaching the code-pairing?
And I reflectm on my own biases, thus this observation.
The most confusing part for me is that I am unable to "clap" or bookmark the articles inside medium when I use incognito, in order to revisit them in a future time.
Bookmarking them in Raindrop is the current solution for me, but still I feel that there is a lot of friction going on.