Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
tuveson
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
61.
▲
by
tuveson
1y ago
It actually seems like there’s another Easter egg if you google “blink tag”: https://www.google.com/search?q=blink+tag (Doesn’t seem to trigger on iOS, but works in Chrome and Firefox on desktop)
62.
▲
by
tuveson
1y ago
Yeah, that's fair enough. I'm sure a lot of weird / bad language design choices can be chalked up to this (COBOL...). Now that C and Pascal derived languages have been around for a long time, even if you don't know about
63.
▲
by
tuveson
1y ago
It’s definitely easier to parse, but you can use shunting yard to do operator precedence parsing using very little extra memory and no recursion. I feel like the language is just poorly designed.
64.
▲
by
tuveson
1y ago
Why is the bar serving frozen pizza?
65.
▲
Show HN: 10k Lines of Basic
(10klob.com)
2 points
by
tuveson
1y ago
|
0 comments
66.
▲
by
tuveson
1y ago
C is not as hard to get into as you might think, and probably necessary to be at least a little bit comfortable with if you want to write Python libraries or understand Python internals. I would suggest Beej’s guide, if you’re looking for a
67.
▲
by
tuveson
1y ago
Oppenheimer had sex and explosions, but the banter part might be more subjective
68.
▲
by
tuveson
1y ago
There are plenty of places where it makes more sense to use DSLs (or where they’re flat-out required). SQL and regex both spring to mind. Pretty much any HTML templating language is simpler to use than concatenation a bunch of strings toget
69.
▲
by
tuveson
1y ago
FreeBSD must be pulling a very long con, then.
70.
▲
by
tuveson
1y ago
Sorry, but I'm not sure which dialect of BASIC this is - wish I could be more helpful here. TinyBASIC is a very minimal implementation (no arrays, functions, nor loops) so it definitely won't be able to run this program.
71.
▲
by
tuveson
1y ago
If anyone is interested, I just wrote a TinyBasic implementation: https://github.com/danieltuveson/dbi
72.
▲
by
tuveson
1y ago
I think Balatro uses the Love2d engine which is in C/C++.
73.
▲
by
tuveson
1y ago
Thanks! It's called fib, so there's sort of a double meaning there.
74.
▲
Show HN: Dan's Basic Interpreter
(github.com)
3 points
by
tuveson
1y ago
|
2 comments
75.
▲
by
tuveson
1y ago
I unwittingly chose an example that allowed you to write fewer s-expressions in Lisp… touché.
76.
▲
by
tuveson
1y ago
How would you write this in Lisp without introducing a bunch of parens? `if (0 <= x + m && x + m <= n) {…}` I’m not a Lisp hater, but there’s a reason people make this criticism. I think most people find the infix version easi
77.
▲
by
tuveson
1y ago
wot if ya mum ran on batteries
78.
▲
by
tuveson
2y ago
Why? It's a static site generator. He controls the inputs - there's basically no attack surface. I can't think of a situation where lack of memory safety would be less of a problem.
79.
▲
by
tuveson
2y ago
> Also, it's definitely not nearly as easy to implement I think this is the real reason why there are so many dynamic language implementations. If you want to implement a dynamic language, you just slap a type tag on your runtime ob
80.
▲
by
tuveson
2y ago
llama.rs, of course /s
81.
▲
by
tuveson
2y ago
> When I read the article it was very clear, due to the compiler's in-memory graphs, that they needed a GC. It's actually pretty easy to do something like this with C, just using something like an arena allocator, or honestly,
82.
▲
by
tuveson
2y ago
> untyped references to strongly typed values I would call that weakly typed since there is no step before your code runs that validates (or even tries to validate) that your program satisfies a "type system". But since the def
83.
▲
by
tuveson
2y ago
For parity, C should add a `prefer` keyword that hoists statements to the top of the function.
84.
▲
by
tuveson
2y ago
Maybe surprising to hear white people saying it, but most black people (or people who grew up in predominantly black neighborhoods) throughout the US have been using it for a long time. I would assume that's a byproduct of The Great Mi
85.
▲
Stupidly Typed Programming Languages
(danieltuveson.github.io)
17 points
by
tuveson
2y ago
|
6 comments
86.
▲
by
tuveson
2y ago
Step 1: write an RFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFC Step 2: write an RFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFRFC …and so on
87.
▲
by
tuveson
2y ago
I think the real problem on Twitter is the massive amount of spam that now exists. It's much worse than it was a couple of years ago. If all it consists of is bots and hucksters that pay to appear at the top of viral posts, it will cea
88.
▲
by
tuveson
2y ago
For n<=8, GCC will also just inline it for the naive version in C: https://godbolt.org/z/TvdcTvEKx
89.
▲
by
tuveson
2y ago
I disagree. The conventions for declaring arrays, pointers, and function pointers are all idiosyncratic. In C, the type is always to the left of the variable being declared. Except for arrays, which have part of the declaration to the right
90.
▲
by
tuveson
2y ago
Fast to compile, fast to run, simple cross-compilation, a big standard library, good tooling… As ugly and ad-hoc as the language feels, it’s hard to deny that what a lot of people want is just good built-in tooling. I was going to say that
More ›