All right, I got nerdsniped into writing a "yes and" sort of thing even though I agree with the gist of this article :) https://macwright.com/2025/08/21/why-d3-is-so-verbose-anothe...
Readit Newstmcw commented on Why is D3 so Verbose? theheasman.com/short_stor... · Posted by u/TheHeasman
tmcw commented on Show HN: Atlas – GIS and interactive maps in the browser atlas.co... · Posted by u/vloewe
I have a stupid dream.
I really want a news application that is rendered visually as the Globe. Then a user can drag, zoom, and pan around the world, similar to Google Earth.
The difference being, this news app overlays current trending news stories on the physical location of where it is happening in the world.
Maybe I can manage this idea with this underneath?
Development Seed did this a long long time ago in Drupal: https://web.archive.org/web/20130430031803/http://managingne... https://www.drupal.org/project/managingnews
tmcw commented on Placemark is going open source and shutting down macwright.com/2023/11/13/... · Posted by u/Tomte
Can someone shed some light on what happens monetarily to bootstrapped company founders? How many of them are offering personal collateral on loans vs some form of angel investing? I'm finding it hard to square open sourcing something if someone just lost decades of savings or the value in their home, so I'm curious if there's some way they're getting funding for their companies that doesn't ruin them if things like this happen. The tone is also very, "I lost dreams but not my livelihood" in many of these statements and I'm curious how.
I did consulting for the first 8 months of development, and then the company roughly broke even for operational costs since day one. I built most things myself which led to lower costs. My main cost was just rent and health insurance, which in America, self-employed, is both expensive and useless. I had savings from working for a decade in tech and minimized other costs. So, lucky position to be in, but also your average startup's monthly burn is enormous compared to what you can do by being scrappy.
tmcw commented on Placemark is going open source and shutting down macwright.com/2023/11/13/... · Posted by u/Tomte
Given your setup would it be easy to make a data exporter/importer? That way you could give them the data and shut down before opening the source.
Placemark was built around that idea - all the data is easily exportable & importable in many open formats. It should be straightforward to move to the open source version or other tools.
tmcw commented on Placemark is going open source and shutting down macwright.com/2023/11/13/... · Posted by u/Tomte
Looks a bit too ambitious. Was it really necessary to provide collaborative real-time editing? This feature seems way over the top.
I understand every startup wants to have a killer feature which creates unique selling proposition, but this seems like something that probably took way too much effort and wasn't really demanded. But this is only my assumption.
That's a fair assumption. There were some customers who benefited from real-time editing, but it was a big tech bet and led to a design that was harder to scale for larger datasets.
tmcw commented on Placemark is going open source and shutting down macwright.com/2023/11/13/... · Posted by u/Tomte
The concern may be that there could be undiscovered vulnerabilities in the service and releasing the source before shutdown could make it easier for malicious actors to discover those vulnerabilities and compromise user data.
Yes, that's the rationale. A customer has asked about getting access to the source ahead of time and I'll try to make that work.
> It's also - in terms of performance - super fast
Kysely is also super fast. Your bottleneck will always be database requests. If you're chasing every milli, why node.js?
> the extra database drivers being core and developed as part of the main project.
Kysely's dialects are dead simple to implement on your own. As evident by all the 3rd party dialects being open-sourced and all the comments from people using Kysely in production with stuff like cockroachdb, mariadb, clickhouse and such.
Its unhealthy to maintain niche database knowledge in the core. We just don't have the time (FYI we do this for fun, not trying to catch all the sponsors and get VC funded) to play around with all of these technologies, and stay up-to-date with changes.
Both Sami and I have submitted pull requests in 3rd party dialect repositories in the past. I maintain a few dialects on my own.
> It supports prepared statements, which is awesome.
In connection pooling scenarios Kysely was mainly built for, prepared statements are arguably "not that great". In FaaS, a burst of requests might make your database work extra hard, as each new lambda instance comes with brand new connection/s.
> I prefer the way that it lets us write parts of queries, and compose them - like you import expressions like "and" and "eq" and you can write and(eq(users.id, 'x'), eq(users.name, 'Tom')) and you can actually stringify that to the SQL it generates. Or you can do a custom bit of SQL and use the names of table columns in that, like `COUNT(${users.name})`. I can't say scientifically that this is superior, and it's almost a little weird, but I've really found it a nice way to compose and debug queries.
This has been part of Kysely for a while now, and is only getting stronger with new `ExpressionBuilder` capabilities. The fun part is, you don't have to import anything, and are not coupled to your migration code.
Personally I like both projects, as I hope I made clear in the OP - I sense that there's some history and strife here that I'm not clued into as an outsider.