fiedzia

10 ms·

91.
by fiedzia 3y ago
> without using a bunch of excess thread context resources If the threads are cheap, there is no point in making this distinction, which greatly simplifies the language. And they can be, we just need programming languages designed for th
92.
by fiedzia 3y ago
Don't. My rule is if it's more then 3 lines or more complex than simple commmand call, it'll be written in Python. It will be easier to read for everyone around and avoid all the shell footguns.
93.
by fiedzia 3y ago
For one-time dump of everything, that would work fine. For keeping in sync regularly, look at Dolt (google "git for data" for more solutions like this one, there are a few already).
94.
by fiedzia 3y ago
> Why not just use SQLite directly? SQLite does not provide replication, so there is no way to use it directly (other than copy whole file). If you mean it as "Why not use it as a database" than sure, you can use it directly, t
95.
by fiedzia 3y ago
> # you would have to be a psychopath to pass this > # anything but a User object > def grant_admin_privileges(user:) I had an app once where we used user objects, and later switched to ids to save db calls. Now you have some funct
96.
by fiedzia 3y ago
> Sure, you no longer have to use the await keyword, but it's just a keyword. It is not. It splits ecosystem and you can't easily mix sync and async libraries. We need green threads at language level to fix that.
97.
by fiedzia 3y ago
> Productivity and Scalability(in performance sense) aren't opposites. They often clash with each other. Rust for example is a lot less pleasant to debug than interpreted languages and that is a loss of productivity.
98.
by fiedzia 3y ago
and Dropbox with Python
99.
by fiedzia 3y ago
It's easy to believe (and probably true) that there are some low-hanging fruits in a place nobody looked at before.
100.
by fiedzia 3y ago
> If you can't reliably run production on localhost I don't need to run all of production, just enough of it to get the job done with no shared parts. That's usually very little.
101.
by fiedzia 3y ago
Wasm changes nothing here. Your docker image will have exact same problems as wasm file. If some service preloads 10GB of data and takes 2 mins to start, wasm alone won't magically make it better, smaller or faster. > 30+ lambdas al
102.
by fiedzia 3y ago
Postgres can run arbitrary code too, but at this point it just makes more sense to create a service that acts as a database and translates sql to whatever (people already do that). This however makes whole game pointless, as we are back whe
103.
by fiedzia 3y ago
It's no match for lucene (in practice ES or Solr) in terms of performance and features, as it's very different model of indexing and operating. Keeping it running while 1000s of customers run search queries AND the app uses db AND
104.
by fiedzia 3y ago
It's not the first bug of this type: https://www.engadget.com/2015-12-18-log-into-most-any-linux-... I recall Gnome had similar issue, though can't find a link right now.
105.
by fiedzia 3y ago
3. should be one click in your IDE.
106.
by fiedzia 3y ago
The case for any other shell: ls -R and find exist and work. Nushell doesn't cover that. I like the idea, but execution has so glaring holes that I had to go back to fish 1 min after installing nu. (there is glob ** that doesn't h
107.
by fiedzia 3y ago
> If the system you're working on is small, and going to stay small, then that doesn't matter. Having good default solution saves a lot of problems with migration. Storing files outside of database today really isn't that
108.
by fiedzia 3y ago
>Think of it as having a new database column type where you can store files of any size, and behind the scenes they are stored in AWS S3 and cached through a global CDN. So the files are not stored in the database, but somewhere else. Th
109.
by fiedzia 3y ago
> If you mess up the backend (data corruption, data removal, data leaking, etc.) you are in hell. True, but also tooling is better. I have seen a data corruption in a database only once in my life (at least in production). Finding some i
110.
by fiedzia 3y ago
The issue is simple to resolve - most ui frameworks will have some sort of virtual table that only display and manage elements user will see, so just use that (react window does that, but there are table variants that are doing all the work
111.
by fiedzia 4y ago
> Just like the majority of the bugs are not prevented using rust, "For more than a decade, memory safety vulnerabilities have consistently represented more than 65% of vulnerabilities". That's not minority. We are getting
112.
by fiedzia 4y ago
> all of us make mistakes and will keep making them, in any language .. unless said language makes making those mistakes difficult or impossible. Sanitizing input for example has not been an issue for me for decades, as every framework I
113.
by fiedzia 4y ago
> using a low budget project with few developers maintaining one of the most used libraries in the whole World as an example of non memory safe languages perils is not exactly honest Why? That's the situation of enormous amount of c
114.
by fiedzia 4y ago
> We can also reimplement everything in JavaScript Look at js package stats - that's exactly what's happening. Many of apps and packages created today in js would be created in C/C++ few years ago. People who learn program
115.
by fiedzia 4y ago
> Implementing a linked list in Rust is somewhat challenging because of the safety issues that arise Implementing linked list in any language that is not memory-safe is challenging because of safety issues. Rust just points it out.
116.
by fiedzia 4y ago
> Cameras are designed to capture & store the light in a way we can interpret later. They intentionally weren’t designed to edit or interpret the light and make corrections. That's one thing, but still there are many features of
117.
by fiedzia 4y ago
> Any kernel that did panic would stop getting used by the majority of people pretty fast as being "too unreliable". So will kernel that corrupts data, but panic is much easier to fix than corrupted data because it's close
118.
by fiedzia 4y ago
> There are some people who would prefer the purity of "Panic" on a memory corruption/error, If the OS will encounter memory corruption, it cannot reliably do anything but restart. Anything else will risk further corrupti
119.
by fiedzia 4y ago
> When I read memory safe it means that it cannot happen at all, and therefore I don't have to think about that kind of stuff when I write a program. I've never needed to use unsafe in my Rust applications, which means that my
120.
by fiedzia 4y ago
> they told you that Rust is a memory safe language and you don’t need anything else than the rust compiler - this is how I find 99% of today’s articles about Rust. It is - as long as you don't use unsafe. Which is very rare, so we&

More ›