Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
JaggerJo
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
JaggerJo
11mo ago
The code snippet is in F#. And F# has so called "computation expressions".
32.
▲
by
JaggerJo
11mo ago
To me it's crazy how many people work on these seemingly simple applications. How many people do you need to build JUST the native Android and iOS app for snapchat? Is the "single" codebase really worth all the added complexi
33.
▲
by
JaggerJo
11mo ago
Excellent Points, this is where the answer is "it depends". > What do you put in the common core? Android does HTTP requests one way. iOS does them another way. You go for the lowest common denominator an implement a third way,
34.
▲
by
JaggerJo
11mo ago
Agreed. One extra clarification: If the quality of your app is business critical you should really use the native UI toolkit to offer the best platform integration and user experience. If your app is not business critical (you just have to
35.
▲
by
JaggerJo
11mo ago
Just write 2 native UIs in the 2 platform native languages and share a common core written in any language that offers a C like FFI. How hard could it be?
36.
▲
by
JaggerJo
11mo ago
How does it render pixel data to the terminal? I've stumbled over sixels [1], but movy seems to use something else that also enables color output and a higher resolution? [1]: https://en.wikipedia.org/wiki/Sixel E
37.
▲
by
JaggerJo
11mo ago
great writing style
38.
▲
by
JaggerJo
1y ago
I don't have any sleep issues as long as I stick to a simple rule: No caffeine after 15:00.
39.
▲
by
JaggerJo
1y ago
Interesting!
40.
▲
by
JaggerJo
1y ago
Cool project!
41.
▲
by
JaggerJo
1y ago
Yes, that would be even better - but also way harder for unit tests as you’d need to interop between the langauges.
42.
▲
by
JaggerJo
1y ago
> .. excluding all tests and examples, .. How would you verify that the ported code actually works if you don't port the tests and examples? I see tremendous use in a tool that could be used to port "any" library to any la
43.
▲
by
JaggerJo
1y ago
Zig would be my go to language for low level stuff. I think fact that Zig can be used as a C/C++ cross compiler is brilliant.
44.
▲
by
JaggerJo
1y ago
What on earth do they need this kind of money for?
45.
▲
by
JaggerJo
1y ago
Nice! Had to look twice at the author name. Thanks for all the Avalonia related work you are doing!
46.
▲
by
JaggerJo
1y ago
I agree. Most things that got added are good. I don’t like that there are 3+ ways of checking if a value is null tho.
47.
▲
by
JaggerJo
1y ago
Yeah - I worked on an F# project that was ~300K LoC and tooling speed really becomes an issue at that point.
48.
▲
by
JaggerJo
1y ago
OCaml does not have what you'd call I fully featured GUI framework to my knowledge (besides rendering webpages). F# has FuncUI - based on Avalonia. All just possible because of the ecosystem. https://github.com/fsprojec
49.
▲
by
JaggerJo
1y ago
Did you try F# in JetBrains Rider? It's the best F# tooling you can buy IMO.
50.
▲
by
JaggerJo
1y ago
DarkLang which was initially written in OCaml eventually switched to F#. From what I remember the main reasons were the library ecosystem and concurrency. I'm know .NET in and out, so I might be biased. Most of the boring parts have mu
51.
▲
by
JaggerJo
1y ago
Yea, I’d pair it with a contrasting band. Or maybe with one that adds another accent. True. It might be just me but I think the color makes it look cheap.
52.
▲
by
JaggerJo
1y ago
I really like the silver. Red and Blue are IMO not needed as you can always add an accent using the band. Probably just makes everything more complicated.
53.
▲
by
JaggerJo
1y ago
Thanks F#!
54.
▲
by
JaggerJo
1y ago
Just buy a Rider license. Never looked back.
55.
▲
by
JaggerJo
1y ago
Because a LLM architecture seems way too fuzzy and unpredictable for something that should be reproducible.
56.
▲
by
JaggerJo
1y ago
Yes, this is scary.
57.
▲
by
JaggerJo
1y ago
Same, tried Claud code over the past month. Let it do different tasks. It’s useful as an built-in quick docs / search that can spit out small code fragments. Every time I gave it more space results were disappointing.
58.
▲
by
JaggerJo
1y ago
REST almost never is worth it. It’s a nice idea, but in practice things often are more complicated. API quality is often not relevant to the business after it passes the “mostly works” bar. I’ll just use plain http or RPC when it’s not impo
59.
▲
by
JaggerJo
1y ago
I really like fly.io, but you’d need to provide more information about the kind of backend and the expected load. Also what does it currently cost? I host a few sites on fly for pennies, but they don’t see a lot of traffic.
60.
▲
by
JaggerJo
2y ago
Hah, I'm not so sure about what happens during automatic notarisation. Sideloading would at least allow JIT compilation. The fee only applies to alternative app stores, not simple apps.
More ›