HackerTrans
TopNewTrendsCommentsPastAskShowJobs

jasim

8,107 karmajoined 16 वर्ष पहले
https://protoship.io

https://twitter.com/jasim_ab

[email protected]

Submissions

SQL

remy.wang
3 points·by jasim·पिछला माह·0 comments

Passing DBs Through Continuations

remy.wang
1 points·by jasim·पिछला माह·0 comments

A.I. Did What Super-Specialist Doctors Could Not – Claude Opus 4.6

youtube.com
1 points·by jasim·5 माह पहले·0 comments

Cache-Friendly B+Tree Nodes with Dynamic Fanout

jacobsherin.com
99 points·by jasim·9 माह पहले·30 comments

A B+ tree node underflows: merge or borrow?

jacobsherin.com
43 points·by jasim·9 माह पहले·0 comments

comments

jasim
·17 घंटे पहले·discuss
I hadn't considered that, you are right. Though I would still prefer TS because the language is all about types; the entire ecosystem is well-typed and the type system is quite powerful (I do enjoy an occasional Omit and Pick). But it is a personal choice; as long as LLMs can generate well-typed Python, then for people who like the language it makes sense. However from the article, I got the sense that they went completely dynamic.
jasim
·17 घंटे पहले·discuss
I'm curious about the choice of Python, rather than TypeScript.

I find Ruby a very beautiful language, and Rails is an excellent web framework, but I need typed functions, record types and sum types.

They help not just with correctness, but also as living documentation that lets me understand AI generated code. TypeScript provides discriminated union, but not exhaustive pattern-matching, and its syntax is a bit verbose, but since I'm no longer writing most of the code myself, I can live with it.

However I can't imagine using Python or any other dynamic language going forward. There is likely good reason for you to choose it, and I'm curious to know what that is.
jasim
·14 दिन पहले·discuss
There is no other stack in the last 15 years or so that I look back with the same fond affection as building business applications in Clipper. One important aspect was that software was delivered physically, and I could watch my users using them. If I made a report that helped the operator, or made a workflow easier, their happiness was immediate and nurturing. And there was an immediacy to programming in xBase - if we're building a database backed business application, which was their strong suit, there was very little standing in between us and the problem space.
jasim
·पिछला माह·discuss
"There was no exploit. No vulnerability disclosure. No CVE for me to write. The attacker filled out my signup form 942 times, made 942 workspaces, sent 942 batches of about a hundred invitations each, and stopped. They used my tool exactly as designed. The design was just bad enough that the tool was good for phishing."
jasim
·2 माह पहले·discuss
In my early programming days, working with Clipper, I used to look at Delphi from a distance with awe and a bit of jealousy. There also used to be PowerBuilder and Paradox, as competition to the xBase platforms.

I'd love to hear more about how you're using Delphi and what it excels at, compared to current web and native software stacks.
jasim
·4 माह पहले·discuss
Everytime someone mentions Clipper (or dBase or FoxPro, or even FoxBase, but Clipper the most), I feel a sene of productive nostalgia, and a constructive anger at the state of technology today. xBase was a beautiful thing - I haven't had as much fun at building software that I've had from the first plink86 till CA-Clipper 5.3's blinker and exospace. Even prolific use of Opus 4.6 doesn't bring the sense of quality and satisfaction that those systems produced.

I'm building a new database tool for the web, a frankenstein of Lotus 1-2-3, dBase, MS-Access, and Claude Code. It is where that anger goes these days.