Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kaeshiwaza
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
kaeshiwaza
5mo ago
jj is amazing, even as a solo dev on small projects. It's difficult to explain because it depends of each usage, but it's very easy and safe (you can undo everything) to just try and see.
2.
▲
by
kaeshiwaza
5mo ago
AI is so ineffective that compagnies that use it cannot pay their workers ! Poor guys tech bros.
3.
▲
by
kaeshiwaza
1y ago
Taking a pause also... I don't believe serving IA can be aligned to serving devs. I hope that the part of the work related to the core of PostgreSQL will help the community.
4.
▲
by
kaeshiwaza
2y ago
Locality of behavior can be done with few lines of js. https://github.com/gnat/css-scope-inline
5.
▲
by
kaeshiwaza
2y ago
I use Fluxbox since the first version. Very easy to customize. I've just an issue with Firefox, the Firefox windows doesn't want to play with Fluxbox (on Debian)...
6.
▲
by
kaeshiwaza
3y ago
Maybe the new feature 'hx-on' can help with that ?
7.
▲
by
kaeshiwaza
4y ago
As we use less and less Javascript, thanks to htmx, i'm no so reluctant to use vanilla JS when needed.
8.
▲
by
kaeshiwaza
4y ago
I'm using htmx in production since one year. From game (scrabble game with board refresh, chat and so on -with sse extension-) and cms to professional crud apps. With Go + stdlib template. Now looking at PWA, it seems to fit very well.
9.
▲
by
kaeshiwaza
4y ago
I can replace all the iframe from my legacy apps without changing any logic !
10.
▲
by
kaeshiwaza
4y ago
Rendering html doesn't consume a lot more than rendering json, specially that with htmx you'll render small fragments... Anyway the bottleneck is most of the time on the database.
11.
▲
by
kaeshiwaza
4y ago
I still work like that 30 years after, thanks to Go... I would not like beginning today !
12.
▲
by
kaeshiwaza
5y ago
It's where Thomson-Unix way win as KISS and still work for small to large scale.
13.
▲
by
kaeshiwaza
8y ago
Maybe they have other future projects with Go ?
14.
▲
by
kaeshiwaza
8y ago
In large software you'll not do go get -u for all packages, you'll upgrade each package separately, at the maximum version or at a specified one. It's just that it's you the user of the modules will choose what and when
15.
▲
by
kaeshiwaza
8y ago
Dep has also issues, it's safer to continue to use Dep when you already use it but for new project it's recommended to switch now to go modules. Anyway, most of the time it doesn't change anythings to lock the version with d
16.
▲
by
kaeshiwaza
8y ago
It was a long series of "i will say you my concerns tomorrow" that just make stir up the sauce since month without any clear and obvious problem.
17.
▲
by
kaeshiwaza
8y ago
The implementation of vgo (so simple) cannot be compared to dep. It can explain why it was more easy to just do it than spend time to explain. It's often like that in dev, when we find a simpler solution in our own code we just do it a
18.
▲
by
kaeshiwaza
8y ago
I have exactly the same feeling. And remember at the time of the start of Dep that there was no consensus and a big hope that the final integrated solution will be more Goish than Glide. Very surprised by the begin of Dep. I don't beli
19.
▲
by
kaeshiwaza
8y ago
You didn't find example of failed Cargo because most of the time it just do like go get -u, and solve a non-problem !
20.
▲
by
kaeshiwaza
8y ago
Upper bound are major version, everything between should be api compatible (it's in the specs of go modules).
21.
▲
by
kaeshiwaza
8y ago
You'll find a go.sum with hashs of dependencies.
22.
▲
by
kaeshiwaza
8y ago
It's a feature not a problem. It select the only know working solution. You're still free to update to newest versions.
23.
▲
by
kaeshiwaza
8y ago
Not only buggy, theses tools didn't follow the simplicity that we like in Go. For example gb was more in the Go philosophy for my taste. I was surprise that it was not chosen as the official experiment.
24.
▲
by
kaeshiwaza
8y ago
I've the same workflow, but like you said gopath disappear. You just hate gopath also :-) I mean, with go modules you will have the same workflow but without the need to adjust the envs.
25.
▲
by
kaeshiwaza
8y ago
Parts of the "vocal minority" was also emotional, that doesn't help to focus on the technical args.
26.
▲
by
kaeshiwaza
8y ago
Look at https://research.swtch.com/vgo-tour (Upgrading) vgo list -m -u will show you which newer releases of your dependencies. Then you can upgrade one dependencies vgo get xxx or all vgo get -u
27.
▲
by
kaeshiwaza
8y ago
Looking at the thumbs up and the comments, the community seems very favorable at vgo. https://github.com/golang/go/issues/24301 edit: and everybody was not agree at the time of Dep launch as it was not simple
28.
▲
by
kaeshiwaza
8y ago
I believe this video of rsc explain some concerns about the Cargo's approach and lock file issues https://www.youtube.com/watch?v=F8nrpe0XWRg
29.
▲
by
kaeshiwaza
9y ago
A quick try show me that it's very very slow... Like 1s for a very simple query on a quite small database. I tried from a scaleway server (in France).
30.
▲
by
kaeshiwaza
9y ago
Is it possible to create a replicate user and then replicate to a local server ?
More ›