Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
crad
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
crad
5y ago
Does it run on / require Yggdrasil Linux? (asking with tongue in cheek)
32.
▲
by
crad
5y ago
I use a combination of: - Graphite - InfluxDB - PostgreSQL - Timescale - CloudWatch - Prometheus The alerting in Grafana supporting all those variations is a godsend.
33.
▲
by
crad
5y ago
Looks like it's a thin wrapper on top of boto3 that removes some of the boto-isms.
34.
▲
by
crad
5y ago
Scaling for one. If 95% of your workload is non-transactional reads, why introduce transactions? If your writes are single table and don't require transactional safety, why introduce transactions? If you need complex, multiple-insert o
35.
▲
by
crad
5y ago
Anecdotes obviously don't validate data models, but I do wonder if my personal experience was common. My mother-in-law passed last summer, alone in her apartment. She was sick beforehand, quarantined, and living in a senior living comm
36.
▲
My journey to understand rust-lang
(daveshawley.medium.com)
1 points
by
crad
5y ago
|
0 comments
37.
▲
by
crad
6y ago
I think you missed the point as an opportunity to pitch your project.
38.
▲
by
crad
6y ago
Same here :)
39.
▲
by
crad
6y ago
I read pgRouting as focusing on Geospacial routing to get from point A to point B. Is there more to it than that? A graph database is about storing data that the relationships between pieces of data, like a social graph as an example. You&#
40.
▲
by
crad
6y ago
I get much higher request throughput in my Tornado applications, with very low response latencies, strange.
41.
▲
by
crad
6y ago
Well known in the NodeJS community perhaps - outside of that?
42.
▲
by
crad
6y ago
The push for Python 3 has been happening for over 10 years at this point. At what point do you expect people to be able to stop supporting a very outdated distribution of any software? 6 years ago my company switched to Python 3.5 and there
43.
▲
by
crad
6y ago
Great Post José! I remember early presentations on Elixir (I think first at Erlang DC in 2011 or 12?) and it's been great to watch Elixir mature and develop. While I'm strongly in the Erlang camp, I do appreciate the work you and
44.
▲
by
crad
6y ago
I could see that, my biggest gripe with Erlang has always been around the "softer edges" - easy to grok tooling, easy to read documentation, etc. And something to work on for sure.
45.
▲
by
crad
6y ago
Great post, though as a disclaimer, it mirrors my own biases and thoughts on Elixir. I'm happy for its success, but I too find it a step backward. On the positive side, I don't think we'd have gotten rebar3 without hex guidin
46.
▲
by
crad
6y ago
I've been enjoying the game thus far, albeit on the PC. No issues, no bugs encountered. Granted I'm only 6 hours in, but still. I think people go out of their way to find things to complain and be negative about. Frankly 1.0 relea
47.
▲
by
crad
6y ago
Personally I'm very disappointed that we keep inventing new standards, like pyproject.toml when other things have like setup.cfg, existed for an extended period of time, works well, and is supported for reading and writing by the stdli
48.
▲
by
crad
6y ago
Wasn't part of the MVP, will be in the next sprint. Edit: should clarify, was making a joke.
49.
▲
by
crad
6y ago
Bought my wife the new M1 MBA as a replacement for her 3yo Macbook. She loves it. It's significantly faster for her applications, the keyboard is a return to one she likes, and she's not run into any issues with it thus far. If th
50.
▲
by
crad
6y ago
It's evolved. There was a point that Tom Lane was the last line of defense against anything that strayed too far. Heck at one of Postgres conferences there was a shirt that said something like "Tom Lane reviewed my patch and all I
51.
▲
by
crad
6y ago
In my org, I have created a process to clearly define what makes a prototype different from a MVP. It appears to be somewhat successful for what my goals were, which was to prevent prototypes from turning into long-term production code. Pro
52.
▲
by
crad
6y ago
This is so painful to me. So much of a reinventing the wheel for things that are not broken. :(
53.
▲
by
crad
6y ago
That's awesome! I'm glad it was useful!
54.
▲
by
crad
6y ago
Thank you!
55.
▲
by
crad
6y ago
Thank you!
56.
▲
by
crad
6y ago
Using the opportunity to pimp my book, RabbitMQ in Depth: https://www.manning.com/books/rabbitmq-in-depth :)
57.
▲
by
crad
6y ago
1. There is a significant amount of improvement with regard to performance. 2. The partitioning improvements are tremendous and well worth the change if you're using trigger+constraint based partitioning. 3. Parallelization and the add
58.
▲
by
crad
6y ago
Well that sucks. I'm glad they got an exit. I won't be using them moving forward due to trust issues with Zoom.
59.
▲
by
crad
6y ago
Looks like they got shutdown on Twitter as well: https://twitter.com/popcorntimetv
60.
▲
by
crad
6y ago
Neat, but "instantly" is a bit much. How about quickly? :-p
More ›