Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ywei3410
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
91.
▲
by
ywei3410
6y ago
That's a fair point. I hadn't considered the names at all; I suppose one could argue that a three letter prefix is the least of Java's verbosity woes.
92.
▲
by
ywei3410
6y ago
There's nothing specifically wrong with it; just that dogma without understanding why you're doing it is always problematic. If your coding rules state that /every/ object with any properties needs an associated getter&#
93.
▲
by
ywei3410
6y ago
To add to the other reasons - the CS compiler optimizes different forms and Racket is currently optimized for it's own compiler. To give a concrete example, taken directly from the racket blog [1]: > For example, Racket BC makes dor
94.
▲
by
ywei3410
6y ago
Of course — this paper talks about the mechanism which Racket explores to keep the boundary safe [1]. This paper [2] elaborates on some of the performance challenges. 'Shallow typing' by Ben Greenman et al. is available only by v
95.
▲
by
ywei3410
6y ago
Yes! There is some work being done in this space already; by the incredible people at North-Eastern. One of the more interesting parts of this problem is what you do at the /boundaries/ of the different languages with differing se
96.
▲
by
ywei3410
6y ago
It does exist and it's called Racket [1] and language-oriented programming. You can write prolog-like languages [2], or Haskell-like [3], or even C-like languages [4]. You can even write BNF directly [5] and you can /call/ th
97.
▲
by
ywei3410
6y ago
Have you preferred Nix or Guix (specifically in writing the configuration/managing the system)?
98.
▲
by
ywei3410
6y ago
Anecdotally, a significant number of recent criticisms towards Emacs and vim are that they’re ugly compared to VS code — that seems to be a solid counterpoint to your argument that among users, aesthetics don’t matter.
99.
▲
by
ywei3410
6y ago
This is one of the reasons that many Lisp developers like Lisp code - local structured editing is trivial because if the braces match, then most of the parser doesn't need to deal with the rest of the file.
100.
▲
by
ywei3410
6y ago
Speaking from experience, session/object management is always tricky with ORM's. SQLAlchemy has been good for us; but the usage has been very, very disciplined and doesn't look idiomatic.
101.
▲
by
ywei3410
6y ago
> Isn't there the assumption in this article that tasks will come in faster than one person can deal with them Yes this is an assumption. This isn't important though - you use a queue when you think tasks will have some level
102.
▲
by
ywei3410
6y ago
Sure — for context I’m very comfortable with Haskell, Typescript, Java and Scala, fairly comfortable with Agda, Coq, C and Rust. I don’t prefer Python (the reasons of which I can elaborate, if you’re interested), but I do prefer to do my pr
103.
▲
by
ywei3410
6y ago
Here's a link with a (partial) [1] answer. [1] https://news.ycombinator.com/item?id=24889703
104.
▲
by
ywei3410
6y ago
I think your counterpoint is a good one — but I would argue that it has the implicit assumption that such users will and can delegate to authority. In my own experience this hasn’t been the case — the alternative of the user not underst
105.
▲
by
ywei3410
6y ago
How does the existence of Google Docs and Word say anything about how hard it is to create real-time collaboration on a web application versus a native application?
106.
▲
by
ywei3410
6y ago
I’m skeptical of no-code solutions because every once in a while, a user does something really problematic without knowing that they do — this isn’t a criticism of the user; how can they be expected to understand, let’s say, security, if th
107.
▲
by
ywei3410
6y ago
You could use hydra [1] to set up something like this pretty easily. I did have a setup like this once, but found that escaping the 'modes' with an extra keypress when I only typically wanted to do one or two operations wasn'
108.
▲
by
ywei3410
6y ago
No, because you control the base primitive functions by passing in fns . In more formal terms, you can control the context. If we really cared, it would be trivial to extend this to a typed variant or change the evaluation semantics. Here&
109.
▲
by
ywei3410
6y ago
Hell, to go even further you can implement your own type system on top of Racket's macro system; or better yet, use a macro DSL specifically created for type systems to implement your type system. [1] [1] https://docs.racket
110.
▲
by
ywei3410
6y ago
Well yes — in the same way that you could have had a half-baked implementation of X on a remote desktop; but it’s unlikely because most GUI-based interfaces will bundle with some level of support. For example, I don’t expect Canonical’s Wa
111.
▲
by
ywei3410
6y ago
> There are extensions to Wayland that add missing functionality, but those are compositor-specific. Meaning effectively that each compositor has its own incompatible variant of the Wayland protocol. Well no — this is where I disagre
112.
▲
by
ywei3410
6y ago
I’m not entirely sure that I understand your point. Here are the facts which I think we can agree on. * X11 is a protocol * Wayland is a protocol * X11 and Wayland are not compatible protocols * Wayland protocols are all public * XOrg is an
113.
▲
by
ywei3410
6y ago
Maybe a more concrete example will answer your question. The Wayland protocols are found here [1]. Your compositor will implement some of these protocols and not others. If I’m writing an application I will; possibly through some toolkit, a
114.
▲
by
ywei3410
6y ago
I do believe that the parent comment was unfair; it is possible to implement a compositor without libwayland — but I do think that there is some truth in that the C structures are the de-facto protocol from the client-side. For example g
115.
▲
by
ywei3410
6y ago
I believe you misread my comment; I said that the full-screen, minimize, re-size isn't part of the server-side decoration extension, but was part of a more basic xdg_shell protocol through the configure event. I was objecting to th
116.
▲
by
ywei3410
6y ago
I don't believe that's correct. The move, minimize, full-screen and resize seems to be part of the xdg_shell protocol (which has no extra methods for decorations and is only for window roles etc...) under the configure event [
117.
▲
by
ywei3410
6y ago
> GLFW, GLEW, SDL, etc. all have to implement CSDs now if they wanna work with Wayland. I honestly don't understand what you're talking about here? If you want to get a window on the screen with OpenGL or Vulkan you don't
118.
▲
by
ywei3410
6y ago
While technically correct, this misses the point. Very few features are part of the core Wayland protocol; off the top of my bind, there's the input methods, and a few ways to describe shared memory with the compositor and some callbac
119.
▲
by
ywei3410
6y ago
An insight I had recently while thinking about language, is that the terms commonly used by the developer community can have some unintended and far-reaching consequences. Take the term user-friendly ; which is insidious term in that it la
120.
▲
by
ywei3410
6y ago
Thank you very much for sharing this! It was a really, very well thought out piece. If I had a particular criticism though, I would wonder whether the section on shared environments wasn’t missing the point — as a society we need to have
More ›