belak
Joined 12 years ago
Karma
201
Submissions
42
Member since
Feb 11
Recent submissions
Comment · 11 days ago
Comment · 1 year ago
I'm have no experience with abstracting away the backend, but Dockerizing is actually pretty easy now - there's an offline mode[1] where you can have sqlx generate some files which let it work when there's no DB running.
[1]: https://docs.rs/sqlx/latest/sqlx/macro.query.html#offline-mo...
Comment · 1 year ago
I think you're missing much of the context and are misrepresenting what happened.
As far as I'm aware, there was no crying he didn't want to work with people, but there was a frustration that he was not open to having a Markdown "standard". To the point where he actively opposed efforts to standardize it, at least under the name Markdown[1].
This is legally and technically fine, as he owns a trademark for Markdown, but when you combine the inconsistent application of that trademark (GitHub Flavored Markdown is seemingly fine, but Common Markdown was not), along with him calling it "Jeff Atwood's crusade" and mocking the effort[2], it's not a great look and resulted in quite a few frustrated people.
As an open source project, you're right that he doesn't owe anything to anyone, but that doesn't mean people have to be entirely happy about how the situation was handled either.
[1]: https://blog.codinghorror.com/standard-markdown-is-now-commo...
[2]: https://soundcloud.com/thetalkshow/ep-88-cat-pictures-side-1, around 1:15
Comment · 3 years ago
They introduced Bitbucket Pipelines around when I left, about 7 years ago.
- https://bitbucket.org/product/features/pipelines
- https://bitbucket.org/blog/introducing-bitbucket-pipelines-b...
Comment · 4 years ago
That's fair - I added "are working on a specific problem which needs a more complicated setup" to my original comment as a nicer way of referring to edge cases like search engines. I still believe that 99% of applications would function perfectly fine with a single primary DB.
Comment · 4 years ago
This is absolutely true - when I was at Bitbucket (ages ago at this point) and we were having issues with our DB server (mostly due to scaling), almost everyone we talked to said "buy a bigger box until you can't any more" because of how complex (and indirectly expensive) the alternatives are - sharding and microservices both have a ton more failure points than a single large box.
I'm sure they eventually moved off that single primary box, but for many years Bitbucket was run off 1 primary in each datacenter (with a failover), and a few read-only copies. If you're getting to the point where one database isn't enough, you're either doing something pretty weird, are working on a specific problem which needs a more complicated setup, or have grown to the point where investing in a microservice architecture starts to make sense.
Comment · 4 years ago
The article is great, but the title here has been editorialized a bit. I'm not super familiar with HN, so what's the best way to get that fixed to match the actual article?
Comment · 4 years ago
Thanks! Good catch! I was going off blog posts and didn't see that there was a download for RC1.
Comment · 4 years ago
The original plan was to release in February, but in the Beta 2 release [1], they said this: "Because we are taking the time to issue a second beta, we now expect that the Go 1.18 release candidate will be issued in February, with the final Go 1.18 release in March."
It looks like there are still a few release blockers [2]. I'd imagine RC is fairly soon though.
EDIT: as mentioned by _fz_ below, RC1 has already released. Seems like the full release will most likely still be in March.
[1]: https://go.dev/blog/go1.18beta2
[2]: https://github.com/golang/go/issues?q=is%3Aopen+label%3Arele...
Comment · 5 years ago
It's also available as a mirror at https://github.com/golang/pkgsite. All the golang.org/x/* packages are thankfully available there, making them pretty easy to find.
Comment · 5 years ago
The short version is "it depends". Essentially, each separate Wayland compositor needs to add support for the nvidia driver (or the driver needs to support more standardized APIs).
Gnome and KDE support Wayland on nvidia hardware (though it's a bit rough around the edges). Wlroots (and therefore Sway) doesn't because they don't want to have a separate code-path for one driver which doesn't want to support standards and because the APIs the driver does support wouldn't work well with the code model of wlroots.
Comment · 6 years ago
I've seen endlessh[0] referenced in the past. Here's an article that talks about this and other SSH tarpits[1].
Comment · 6 years ago
Oh cool, I missed this in the 1.14 release notes. This partially fixes it, but it's not easy to implement multiple interfaces with overlapping functions because you still can't implement multiple functions on the same type with the same name.
Comment · 6 years ago
On your website, the only remote position listed is Senior QA Analyst. Are other positions open for remote work, or only the ones explicitly listed?
I know it's all speculation, and this does come across as more monetization creep, but I can't help to wonder if there's an underlying reason beyond "line go up".