Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dpix
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
dpix
5y ago
This has THE MOST satisfying sounds of any game I've ever played
2.
▲
by
dpix
5y ago
Been a few years now since I've worked much in C# but these all seem like things that should be linting rules. Can these be added as warnings to the compiler? Can you have custom lint/compiler warnings from the community like esli
3.
▲
by
dpix
5y ago
I wonder how fault tolerant maglev systems are. The tracks must have to be incredible straight and precise to have a train hovering over it at 600km/hr over those kinds of distances. With traditional rail it's relatively simple to
4.
▲
by
dpix
5y ago
Congrats on the launch, looks great! Couple of questions: 1. Do you support localization? 2. Do you think there is a benefit to using this in addition to a headless CMS that is already managing authored content? At my previous company we di
5.
▲
by
dpix
5y ago
I don't think the author is trying to call out SQLite as somehow better than others database tech - just that most people perceive SQLite to be a tool for development or exploration when in fact it much more powerful than most believe
6.
▲
by
dpix
6y ago
Love this idea, the site would make for a great place to buy high quality second hand goods that you know would last too. I'm a developer and would love to help out building the site if you are interested, email is in my profile
7.
▲
by
dpix
6y ago
This seems quite subjective - I have worked with services like these and would probably call that SOA where you need to split code concerns along domain boundaries. In the example above, I would probably use cloud functions or a distributed
8.
▲
by
dpix
6y ago
Totally agree, I find a lot of tech is like fashion - leaving and returning again later with a new cooler name. just doing it because it made sense. This ^^. Call it what you like - if it works, it works
9.
▲
by
dpix
6y ago
You are right! Sorry typo fixed
10.
▲
by
dpix
6y ago
This is a great article - One thing I always try and vouch for is that you don't need to go "all-in" on microservices. There is nothing wrong with having a main monolithic application with a few parts separated out into micro
11.
▲
by
dpix
6y ago
Seems like the major win for this chip is having Memory so close to the CPU - on the same chip. This would also be a massive win for cloud computing too, does Amazon/Azure/GCP have anything in the works for introducing ARM chips w
12.
▲
by
dpix
6y ago
Maybe it's just me, but I'd rather all these tech companies that implemented dark mode over the last year or so had worked on new features or bugs instead...
13.
▲
by
dpix
6y ago
The author talks about how many other sources of bug there might be outside of your code like integration, assumptions, compilers etc that e2e tests will help catch. Well at least a large portion of those bugs might be able to be caught by
14.
▲
by
dpix
6y ago
Am I agreeing with you then? You didn't make your position very clear. I'm just stating what I think about wage inequality and class gaps. If you're asking for an actual number of the price of a Cheeseburger and a Shake? I do
15.
▲
by
dpix
6y ago
As much as it costs for employees to be paid sufficiently. It seems awfully dangerous to think that we should pay people less because otherwise things would be expensive. This is exactly why/how wealth is moving up and up to a smaller
16.
▲
by
dpix
6y ago
Doesn't this just encourage more plastic dumping into waterways? Now you can write it off because "it wont harm fish anymore" Lets create systems where we don't need to dump plastic in waterways at all.
17.
▲
by
dpix
6y ago
Isn't there some amount of trust in backers using kickstarter that the funds are returned if they don't reach their targets? While this looks great, it seems like you are donating directly to the creators. Are people willing to ha
18.
▲
by
dpix
6y ago
Yep! that is exactly what our system also does. QA sign off and automated tests run against our preview env. We aren't pushing PRs to prod. It's just hard to justify the validity of a preview env if the deployment is different to
19.
▲
by
dpix
6y ago
Looks interesting but seems like it mainly fits with a docker style deployment? Does this also work with serverless tech? At my current company we have a CI/CD setup that also deploys a per-PR environment - uses terraform and gitlab pi
20.
▲
by
dpix
6y ago
Discussion during the outage: https://news.ycombinator.com/item?id=23161623
21.
▲
by
dpix
6y ago
One problem I have with that hype cycle diagram is that it appears to show that all technologies that get a lot of hype will eventually even out and get good adoption once they go through some growing pains. Realistically though a lot of ne
22.
▲
by
dpix
6y ago
This is awesome? Can anyone explain why all the notes are strung together with glissando? (like a slide on a guitar). I assume it somehow cannot react fast enough to produce the notes separately without sliding between them
23.
▲
by
dpix
6y ago
Reminds me of this great piece by the late Aaron Schwartz - http://www.aaronsw.com/weblog/hatethenews News (particularly in the US) is so caught up in Politics that no one ever knows what anyone's policies are any
24.
▲
by
dpix
6y ago
I agree, I don't think it's malicious and Slack did the right thing here. My comment was more of a dig at Github specifically. Recently things haven't been working for me (from my perspective an outage) and when you go to the
25.
▲
by
dpix
6y ago
I hope they change the status page from "Incident" to "Outage". Too often lately have I seen status pages (mainly Github) reporting incidents when a feature or site is down completely. Seems like their SLAs are influenci
26.
▲
by
dpix
6y ago
Sure, you can own your own data but if you're serving a public website does it make any difference?
27.
▲
by
dpix
6y ago
I didn't mean it as a completely blanket statement, hence why I said "generally". In my experience it's a lot harder to manage a contract between a db schema and multiple codebases over managing versioned contracts betwe
28.
▲
by
dpix
6y ago
This is actually a similar approach to how next.js deployed to vercel (previously zeit) works by default. Each page or api endpoint is served by an individual lambda function so they can scale up or down independently https://nex
29.
▲
by
dpix
6y ago
The same argument can be made for building separate services too. Could become very difficult to merge data between two services after you had redundant information being saved across the two because of a bad design up-front.
30.
▲
by
dpix
6y ago
Sharing databases across services (micro or not) is generally a pretty bad idea exactly for reasons around versioning. Versioning APIs is a pretty standard way to get around this. If your deployment relies on synchronized service deployment
More ›