WingNews logo WingNews GitHub [2]

profwalkstr's comments

profwalkstr | 2 years ago | on: SUSE to go private

I think Dell went downhill after the acquisition, their hardware quality is junk all across their line: servers, workstations, laptops, monitors, etc. Every device from them that I had my hands on recently have, at best, terrible build quality, and at worst, multiple failures. And their support is a bad joke.

profwalkstr | 2 years ago | on: Google Cloud Workstations managed development environment is now GA

Shocked about the prices. Outside of AWS/Azure/GCP, many companies offer bare-metal dedicated server, with very high specs and would cost a lot less (around $40-60) per month. And they can be used as remote workstations.

I myself use a Hetzner server as a remote workstation, which I connect via RDP. 12 cores Intel processor, 64 GB RAM, 2x1 TB HDD and 2x512 GB SSD for US$ 60. If there’s any hardware issue it’s their problem and they will fix it really quickly, so I don’t have to worry about it.

GCP/Azure/AWS prices are insane.

profwalkstr | 2 years ago | on: Ask HN: Is PostgreSQL better than MySQL?

MySQL has a lot of gotchas, WTF moments, things that don't make sense and seem overly and needlessly complicated compared to PostgreSQL.

- Take data types, for example. Seems something simple, right? You can grok all data types in PostgreSQL in an afternoon. Want to grok MySQL data types? You're going to waste an entire week to grok them. There are multiple data types that seem to do the same thing with very small differences and a lot of incompatibilities... and a lot of exceptional behavior (see point below). MySQL data types are LESS powerful, less flexible and 10x more complicated than PostgreSQL data types.

- Enums and sets need to have their possible values defined on a table by table basis. What a nightmare to keep them in sync. PostgreSQL allows you to this once for the whole DB.

- Open MySQL manual and it's full of passages like: feature A does "blah" if X mode is enabled, but does "bar" if mode Y is enabled and will corrupt data if storage engine is used with mode Z enabled.

- SQL strict mode can be disabled by the client. You cannot enforce that your server will work only with SQL strict mode on because a client can simply open a connection with SQL strict mode off. There's no way to enforce that clients will only use SQL strict mode. You have to trust your clients. (This other comment explains strict mode: https://www.reddit.com/r/PostgreSQL/comments/xblooo/comment/...)

- According to the manual, if client A does stuff with strict mode on and client B does stuff with strict mode off, data corruption will occur.

- A lot of surprising and unexpected behavior, even with SQL Strict mode on

- String comparison is case insensitive. There are workarounds but they are still workarounds.

- A lot of behavior is dependent on server configuration. So switching between servers you can't expect them to behave the same.

- Behavior not standardized among versions and installs

- Changing the server SQL mode after creating and inserting data into partitioned tables can cause major changes in the behavior of such tables, and could lead to loss or corruption of data

- Useless error messages (see https://www.reddit.com/r/PostgreSQL/comments/xblooo/comment/...)

- MySQL, at the same time it is less powerful and flexible, has a lot more levers and knobs than PostgreSQL. PostgreSQL, while more powerful and flexible, conceptually is a lot simpler than MySQL.

- PostgreSQL stays out of your way; with MySQL you’re constantly fighting it

PostgreSQL -> simplicity

MySQL -> complexity

profwalkstr | 3 years ago | on: Google Public NTP

I’d rather use time.cloudflare.com. Given Google’s history, we never know when they might discontinue it and send it to the graveyard.
page 1
more