1,124 karma · joined November 14, 2020
The ability to pause a thread from outside is interesting, but it doesn’t seem very useful in general.
It also comes with risks. What if it’s holding a lock? That could cause a performance/latency disaster.
> Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.
You mean for generating unique primary keys? Why would last insert row id be slow?
> and in cases where transactional scopes are required
Could you elaborate on what you mean by this?
https://levlaz.org/sqlite-db-migrations-with-pragma-user_ver...
Do you have some benchmark results by any chance? Although it’s a bit of a can of worms, and I would understand if you didn’t want to get into it at this time.
Not a great choice of API IMHO, but it’s a database, I’ve seen much worse.
On other occasions, they just hijack the name. Like they did with dstat.
If this is true, these companies are responsible for thousands of deaths, and should be prosecuted.
I have a couple of years of experience working with that, and I strongly disagree.
It’s also quite buggy. I’ve hit crashes several times while working with large drawings.
There are better examples of desktop OSS that beat proprietary ones: Blender, vlc, ffmpeg+Handbrake, Firefox, 7zip.
Nowadays I think even Microsoft is more friendly with its users than Linux desktop developers.
Also, please block double tap/triple tap. They trigger zoom in, then it’s impossible to zoom out.
For programming/tech related topics, I no longer use reddit these days, instead just read HN and some blogs. The community is nicer here.
Translating between natural language and SQL is a reasonable idea. I was thinking about this as well, but I didn’t try anything as I don’t have an ML background. I spent some time looking at the SQL side of the problem, and it seemed quite a rabbit hole.
If you do manage to get it working up to a point where it’s usable by the average person, you can take it one step further: auto generate simple apps or websites in a no-code product.
This might bring some hate from the dev community as we are automating ourselves out of a job, but it would be a pretty impressive product if it worked.
Older ways of messaging, like IRC, were not focused so much on notifications and having a full message history that you had to go through when signing in. This forced people to use specialized forms of communication (video meetings, emails, wikis) for important information. Chat was used for casual stuff, for which it works well.
But this kind of corporate robot attitude is common for Google. It’s always the same story with them: they deprecate some service, write a heartfelt message about how they are aware this might destroy some projects/businesses and how difficult it was for them to make this decision, but they’re gonna do it anyways. Thank you very much for doing business with Google, have a nice day.
I guess this is the end of the open source project. Chromium was never truly open source, more like free source, but now it’s not even that. It’s just another proprietary software.
Sad to see Google become the old Microsoft.
Cannot agree with this one. For example, different indent size can be misleading and has introduced many bugs that are hard to notice during review. Apple had a security issue because of this.
Interesting. I was aware of various mmap limitations, but I didn’t think about the TLB changes/flushes, which obviously come with an important overhead.
This is like a textbook example of manager red flags that you should check for and avoid when joining a company.
Oh, the horror!
> people are shifting work hours to ones more of convenience (again anecdotal)
They have no shame!
> But even some of my direct reports will slack significantly more if they think I’m not online. Responses that are normally in minutes take hours etc.I have to now probe for updates etc.
This all sounds very familiar. Let me give you another perspective on this.
It’s very stressful and disruptive to be pinged 20+ times a day. While some of those are people asking for my help, which I gladly do, a good chunk are managers and seniors asking for “updates” or checking in just to see “how it’s going”. Like we didn’t have a standup 4 hours ago. Sometimes it’s colleagues asked by the manager to check on others, so that it doesn’t look like they’re too annoying. I know because it’s obvious and I got asked to do the same many times.
The answer is that it’s going great, thank you very much. At least it was until you interrupted me for the nth time today and now I will have to waste time trying to remember what the hell I was doing in that debugging session. Actually no, a timer expired, so now I will have to restart the whole thing from scratch.
So yes, I sometimes stop answering the chat, or close it altogether. Because I want us to hit the deadline and ship on time, since I care about the team’s results instead of seeing how busy my subordinates are and feeling important for nagging people all day long.
A micromanager hurts the company by reducing productivity and team morale. Your subordinates are not “doing leisurely things” during working hours. They are probably brushing up their CV and doing leetcode to find another job.
This made me smile.