Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mekster
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
87 ms
·
571.
▲
by
mekster
5y ago
Interestingly, ever since I've started doing that a few years ago, I don't get a single spam on the catch all domain. The only spams I'm getting are the ones that come to the address I used on many places (mainly used for acc
572.
▲
by
mekster
5y ago
> if it bounces, the user has only himself to blame So your system always makes the least effort and pushes the blame to users. Great. How about just even do a minimal check that is /.@./ so that the basic format is at least th
573.
▲
by
mekster
5y ago
> The compromised version is the PC version where you scale up the design. Not sure what this means. Compromised is when you have less space to cram information in. > The main argument is that the majority of visitors are on mobile. I
574.
▲
by
mekster
5y ago
As in? I'm serious.
575.
▲
by
mekster
5y ago
What work are you even doing to push virtualization performance to its limit? I cab run a Ubuntu server VM at good performance on VMware.
576.
▲
by
mekster
5y ago
Except Mac, macOS and its third party apps are actually better. Windows is always lagging with its legacy burden, Linux on desktop doesn't have commercial interest to begin with. Consoles are pretty much the same unless they have exclu
577.
▲
by
mekster
5y ago
Safari is only good for Netflix for me. It's inspector is just so different from the rest and you can't even have a custom font to be used! because, security... Terminal is almost good but somehow it doesn't vertically stretc
578.
▲
by
mekster
5y ago
Doesn't feel right. Any OS can virtualize Linux, so the host doesn't really matter. Besides, it's usually the software that matters and not the OS.
579.
▲
by
mekster
5y ago
I can't really get that idea though. PC version is the main drawing board to express as much idea openly as possible for the intial design and the mobile version is just a compromise of the idea into a squashed view. Mobile first is ju
580.
▲
by
mekster
5y ago
I've stopped taking it seriously after seeing blogs like this. https://blog.wesleyac.com/posts/the-curse-of-nixos
581.
▲
by
mekster
5y ago
Except, designers tend to create the PC version first to iterate over the intial design, so not sure how one goes to develop mobile first for this case.
582.
▲
by
mekster
5y ago
If you can't like the current PHP, there's probably no language that will make you feel too well. What exactly is so bad about it?
583.
▲
by
mekster
5y ago
Why do you accept it as a given and not customize it?
584.
▲
by
mekster
5y ago
Yes, you can't possibly write triggers and checks on columns across different databases to the point you should be doing all data checks in the app if you're going to support multiple databases. These days, there's docker, so
585.
▲
by
mekster
5y ago
I often see this quoted but I don't see how they compete at all? Or am I just not getting a joke?
586.
▲
by
mekster
5y ago
> you have to learn keybindings, Are people seriously training their muscle memory to the default vim keybinding that is so cryptic I don't know what to say. Since the early days of learning vim, I've changed the "go to en
587.
▲
by
mekster
5y ago
Initialize git and commit on the dir before touching them.
588.
▲
by
mekster
5y ago
If vim or neovim can work as featureful as JetBrains, I'll switch any day. Let me know how to highlight SQL in strings and make tables linked to remote database over SSH and autocomplete table names and column names as I type. And make
589.
▲
by
mekster
5y ago
If you just want the IP on interfaces, "ip r" is sufficient and easy to remember.
590.
▲
by
mekster
5y ago
Will shells or posix standard ever evolve instead of being the obvious gotchas in interviews?
591.
▲
by
mekster
5y ago
So, use zfs on Linux.
592.
▲
by
mekster
5y ago
> The protocol isn't exactly the problem. It's the buggy implementations of Bluetooth stacks and Bluetooth software in embedded devices. The spec is way too complicated at some 3000 pages long which apparently leads to faulty i
593.
▲
by
mekster
5y ago
That's one of the exact phrases you don't want to hear from a tech department. They make tech excuses which were ultimately their own design and tell that's not possible to be fixed.
594.
▲
by
mekster
5y ago
They apparently do. Even if they did hard delete they still should have backups. They just got lazy fixing it after several similar incidents and this one was expected and yet all they do is a tweet saying "good luck building up the co
595.
▲
by
mekster
5y ago
It's just bad design never getting fixed despite several prior incidents except for GitHub's own project which they reverted. Why do they not just give a public/private flag on star data than somehow modifying the data irreve
596.
▲
by
mekster
5y ago
I sometimes decide what to use based on number of stars. It's a trust in the quality of the software. Now httpie is on 2.5k stars and if I only knew about it today, I'd consider using an alternative with 10k stars if there's
597.
▲
by
mekster
5y ago
I suppose you never take a backup because everything should be in ideal conditions. If you consider manual errors as non existent, you need to rethink your design.
598.
▲
by
mekster
5y ago
It's your customer (repo owners) asking for support and throwing it away being busy is just lazy attitude. You had prior incidents and the bugs were left as is and apparently it will happen again.
599.
▲
by
mekster
5y ago
This is laziness on GitHub. If your client asks you for work and you get lazy because it needs some internal modification that could take a day instead of an hour, you just respond it's impossible. Generally that's quite unaccepta
600.
▲
by
mekster
5y ago
I don't like 3-2-1. It's pretty fragile. I don't know how any sys admins can sleep over 1 remote backup. My setup has 4-2-2 and using 2 different backup implementations for the remote, so bugs in them wouldn't be corrupt
More ›