Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
PeCaN
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
42 ms
·
391.
▲
by
PeCaN
10y ago
Something like Sulong¹ in RPython would be really cool and probably entirely feasible—I too am curious if that's on the PyPy team's radar. ¹ https://github.com/graalvm/sulong
392.
▲
by
PeCaN
10y ago
Jython isn't (yet) implemented on Truffle, I believe (and would require basically a rewrite). The approach chrisseaton describes is generally only feasible if you're implementing a Futamura projection à la PyPy or Truffle. That sa
393.
▲
by
PeCaN
10y ago
The STL might be the best programming success story. It used to be awful , but now I rank it among the best standard libraries of any language.
394.
▲
by
PeCaN
10y ago
> A single, standard event loop that literally every library in the ecosystem uses so you don't have to worry about it. Tcl? Erlang/OTP?
395.
▲
by
PeCaN
10y ago
There are less shitty languages. I'd consider mine to be OCaml and Perl (and Rust is growing on me, but I might be in the first phase above). I think, ultimately, this just boils down to “know a lot of tools and use the right tool for
396.
▲
by
PeCaN
10y ago
More like “the world's worst implementation of asynchronous programming is shitty and didn't learn from its predecessors”.
397.
▲
by
PeCaN
10y ago
Curious, how is Pony's GC superior to Erlang? Erlang's GC is already pretty quick (since the heaps are very small).
398.
▲
by
PeCaN
10y ago
I think people tend to think that C lets you go fast because of the tricks it lets you get away with and how “close to the metal” you are. Which is partially correct, but C is also an obnoxiously hard language to optimize because of the f
399.
▲
by
PeCaN
10y ago
The great part about ATS that I wish Rust had is that you can define linear types for C libraries, and in general the type system is strong enough that you don't need unsafe{} sections. See e.g. https://bluishcoder.co.nz
400.
▲
by
PeCaN
10y ago
If you think that's interesting, you might want to check out ATS¹ and Mercury². ATS is wicked fast and doesn't even do some of the optimizations it's theoretically capable of (I think its alias analysis is fairly primitive).
401.
▲
by
PeCaN
10y ago
It depends what you're writing. I wrote an incremental generational garbage collector in C, and rather regretted the time I spent debugging it. If I wanted it to be at all concurrent, I think I would've given up doing it in C. Rig
402.
▲
by
PeCaN
10y ago
I agree. I've thought of writing a CoffeeScript-for-Ada thing with slightly nicer syntax. (I don't dislike Ada's syntax, but it's occasionally quirkier than necessary.) That said, its easy range types and discriminated
403.
▲
by
PeCaN
10y ago
While I agree, getting used to that mode of thought takes time . IME you have to write a lot of Haskell (or OCaml) before it becomes a very fast prototyping language. Of course, it's 100% worth the investment, and I prefer prototyping
404.
▲
by
PeCaN
10y ago
Obligatory to point out that Perl and Perl6 are quite different languages, and the latter is meant to supplement, not replace, the former. That said, both Perls are nice languages. Personally I prefer Perl 5 slightly, but both are fun to us
405.
▲
by
PeCaN
10y ago
In a way, eyes and mouths are like the radicals for emoji. I'm not sure how you'd sort emoji though, since there's no stroke order.
406.
▲
by
PeCaN
10y ago
Most notoriously “ou” and “ough”. We have a solid 14-20 vowels, and 5 glyphs for them. I suppose Spanish, Korean, and Russian might be easier to pronounce and less rote memorization, but you're certainly right about English.
407.
▲
by
PeCaN
10y ago
Doesn't help that at least for me it gets rendered differently in the title on HN and the actual article. That said, I expected something Japanese related, given that it's Candy Japan, but you'd think common fonts would have
408.
▲
by
PeCaN
10y ago
Alternatively, it could mean that Google Translate is not very good. If I had to guess, most Japanese people aren't going to have much trouble disambiguating ‘eat’ from ‘eclipse’. (And as zorceta explains, Chinese uses different hanzi
409.
▲
by
PeCaN
10y ago
I think NTFS can index alternate data streams¹, but yeah, I agree no filesystems are on the level that BeFS was of easy querying and versatility. ¹ I am not sure about this, but https://msdn.microsoft.com/en-us/librar
410.
▲
by
PeCaN
10y ago
Maybe on Linux. OpenBSD doesn't even have procfs, FreeBSD deprecated it, DragonFlyBSD doesn't mount it by default. /proc is a race condition waiting to happen, so I can't really say I recommend using that.
411.
▲
by
PeCaN
10y ago
awk is rather similar in many ways to powershell, actually, but untyped. I agree most of what powershell does you can do with awk, but it's often less pleasant than powershell (in my experience).
412.
▲
by
PeCaN
10y ago
You could probably hack something together with awk, but this sort of thing is exactly why I like powershell a lot.
413.
▲
by
PeCaN
10y ago
Er, it's a world all of us live in. Say, for example, ‘ps’ or ‘ls -1l’. Then you end up using awk, which is rather like a half-assed version of powershell to work around shortcomings with the unix everything-is-a-string design.
414.
▲
by
PeCaN
10y ago
The reason I chose that particular example was not for the database integration (which is very cool) but for the fact that it's actually something I did. Point is, imagine trying to grep anything tabular in bash. Hypothetically, the ou
415.
▲
by
PeCaN
10y ago
Well, yeah, but I mean the concept (grepping in tabular data). If, hypothetically, bash had database integration, ls Columns would probably return something like foo varchar 30 NOT NULL bar decimal 8 baz int 4 Which would be a
416.
▲
by
PeCaN
10y ago
I find it massively useful in practice, even for mundane tasks. For example, the other day I was trying to search the columns of a very large SQL Server table¹ but also needed information about the column type. …\dbo.site> ls Columns
417.
▲
by
PeCaN
10y ago
FAT is not very interesting from a filesystem design perspective (ask someone who doesn't know much about filesystems to try to design one; chances are it will look like FAT¹), so that hardly surprises me. Anyone who buys a book about
418.
▲
by
PeCaN
10y ago
BeFS's metadata support was much different from usual—it was a key/value map attached to each file. NTFS supports extended attributes and alternate data streams, which you could use to do the same thing, but none of the *nix files
419.
▲
by
PeCaN
10y ago
Can we get this unflagged? Seems like a decent piece of investigative journalism IMO.
420.
▲
by
PeCaN
10y ago
> laptop Is that what Macbooks are called these days? Dammit munificent, get it right.
More ›