Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shalabhc
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
20 ms
·
151.
▲
by
shalabhc
9y ago
> text is easily version able and comparable means a lot to me. Don't you really want to do more meaningful comparisons though? I think text is a poor form for versioning and comparison because you always have to mentally extrapolat
152.
▲
by
shalabhc
9y ago
> But for the most part, the reason these great past ideas are not in use is because nobody has made them into a compelling product. I think you're overestimating the market's ability to select good ideas and specifically, prom
153.
▲
by
shalabhc
9y ago
Maria, clay and runkit look interesting - I like the quick iterations and incremental programming they allow. But you're still writing 'text' to manipulate 'data'. An example of something fundamentally different wou
154.
▲
by
shalabhc
9y ago
> what problems have previously been solved And we're worse at identifying what the problems actually are.
155.
▲
by
shalabhc
9y ago
Bret Victor is now at HARC ( https://harc.ycr.org/member/ ) which has an interesting list of projects.
156.
▲
by
shalabhc
9y ago
> the linux codebase be radically smaller ? I believe Linux isn't built the same way the Smalltalk system was. One glaring difference is the use of C - with that you can't get very high level and are always programming at a ver
157.
▲
by
shalabhc
9y ago
Ah, thanks for explaining that. I was always a little confused about the relationship between these projects.
158.
▲
by
shalabhc
9y ago
For some ideas on how you can get fewer lines, see Nile ( https://github.com/damelang/nile ). Nile is a DSL that implemented many Cairo ( https://cairographics.org/ ) primitives using a much more compact f
159.
▲
by
shalabhc
9y ago
An easy way to try ST-72 is in your browser here: https://lively-web.org/users/Dan/ALTO-Smalltalk-72.html and ST-78 here: https://lively-web.org/users/bert/Smalltalk-78.html The above li
160.
▲
Bloom language – disorderly distributed programming with consistency analysis
(bloom-lang.net)
3 points
by
shalabhc
9y ago
|
0 comments
161.
▲
by
shalabhc
9y ago
I'm not talking about performance though. I'm talking about the fact that when given an ambiguous regexp, most engines match it happily and return the longest match, instead of erroring out saying 'ambiguous input provided&#x
162.
▲
by
shalabhc
9y ago
I'm aware of ordered choice in PEGs. I'm not entirely convinced that's a real problem in practice (or am missing some compelling example). E.g. regular expressions can be ambiguous too, but are still used very extensively and
163.
▲
by
shalabhc
9y ago
Is this a limitation of the PEG syntax itself? IOW, is it possible to identify ambiguities in grammars defined as PEGs?
164.
▲
by
shalabhc
9y ago
> I wonder if what is needed is a kind of "side program" that one could use to annotate the main program in very precise ways and ask questions of its execution, or to produce maps or timelines of aspects of its behavior. But n
165.
▲
by
shalabhc
9y ago
> The way Lisp can still win in today's world is not by trying to replace C on the system level, but by "embracing and extending" C at the application level. Interestingly, another current top post on HN is HPAT - A compil
166.
▲
by
shalabhc
9y ago
> And both styles lead to equally unreadable code. Perhaps because the languages used aren't a good fit for these styles?
167.
▲
by
shalabhc
9y ago
> move a bunch of problems from compile time to run time Perhaps this is an artificial dichotomy? What we really want is verification that some properties hold. These properties should be specified in a uniform way, irrespective of the
168.
▲
by
shalabhc
9y ago
> Data Structures Are Antithetical to Functional Programming Interestingly I've heard a similar pov from the 'pure OO' (Smalltalk style) world as well. Specifically avoiding 'data structures' and embracing late b
169.
▲
by
shalabhc
9y ago
> If you want a property to uphold, formulate it as a type. The compiler verifies. Consider two issues with this: 1. How do you verify that the property to uphold is indeed the same as formulated by the type? This is easier for simple t
170.
▲
by
shalabhc
9y ago
> Some classes of problems are masked on a single system. Yes but you can also have IPC failure, syscall hang, single thread hang etc. Instead of treating these as special cases, these could be handled by generic patterns that apply to &
171.
▲
by
shalabhc
9y ago
> There are problems that exist in distributed system environments that do not exist in single-machine environments. Partial failure, concurrency, and latency are three problems that make distributed computing fundamentally different
172.
▲
by
shalabhc
9y ago
Perhaps https://en.wikipedia.org/wiki/Croquet_Project should be included in Chapter 4: https://github.com/heathermiller/dist-prog-book/blob/master/...
173.
▲
by
shalabhc
9y ago
You distribute the image + interpreter. I presume you could strip the image, but haven't tried it.
174.
▲
by
shalabhc
9y ago
Others have answered but interestingly, TDD was 'built-in' to the Pharo tutorial I did a while back. Basically you write a test first, say it calls an undefined method `x.somemethod()`. You push a button to run the test, as soon a
175.
▲
by
shalabhc
9y ago
This may not be immediately apparent, but I discovered that Smalltalk did not fit into the 'programming language' concepts in my head. I think of a typical bytecode VM language as [source code] -> [interpreter] -> [runni
176.
▲
by
shalabhc
9y ago
What do you think are the problems of emacs?
177.
▲
Multiformats – Self-describing values for Future-proofing
(multiformats.io)
2 points
by
shalabhc
9y ago
|
0 comments
178.
▲
by
shalabhc
9y ago
See https://github.com/howl-editor/howl/issues/68#issuecomment-1... for instructions to build on OSX. The issues have since been ironed out afaik, but I haven't tested recently.
179.
▲
by
shalabhc
9y ago
Question for all static or dynamic typing proponents: do you see your language/type-system as a great and scalable way to program large distributed systems in 10 years? 20 years?
180.
▲
by
shalabhc
9y ago
> But building this model is still programming. I agree with you, but I don't think this is a mistake in the article. I read it as normal programming code meaning low level procedures as are typically written these days.
More ›