HNHacker News
TopNewBestAskShowJobs

fusiongyro

5,495 karma · joined September 17, 2008

Daniel K Lyons

http://www.storytotell.org

Feel free to email me at fusion at storytotell dot org.

[ my public key: https://keybase.io/fusiongyro; my proof: https://keybase.io/fusiongyro/sigs/aYrkbCZouBBhqp_qOKPGdBfIn---A8P8wPVCKLSlpnA ]

submissionscomments
fusiongyro··on Oracle Tells White House: Stop Hiring Silicon Valley People and Ditch Open Source
How likely is this message to be taken seriously?
fusiongyro··on Ask HN: Is Vagrant dead or dated? Do people still use it?
Where I work, getting Vagrant working is more feasible than getting Docker working, because we're stuck on a pretty old RHEL that doesn't have a new enough kernel to run Docker but does have VirtualBox in the standard image. I certainly have a sense that the latter is eating the former's lunch, but we are still using Vagrant for testing and I still like it. I last used it a couple months ago to help a friend get started with PHP. It's a very good replacement for things like MAMP that embed a database, web server and programming language for new developers.
fusiongyro··on The Serverless Revolution Will Make Us All Developers
The same tired argument has been made every decade since the 70s, with mostly the same cast of characters: artificial intelligence, English somehow being used to specify the behavior, stock libraries of code, etc. I think we're about as far from it today as we were when Prolog was a big deal.

The amount of incipient complexity in programming has been growing, not going down. What's more complex, "hello, world" to the console in Python, or "hello world" in a browser with the best and newest web stack? Mobility and microservices create lots of new edge cases and complexity—do non-programmers seem particularly well-equipped to handle edge cases to you?

The problem has never really been the syntax—if it were, non-programmers would have made great strides with Applescript and SQL, and we'd all be building PowerBuilder libraries for a living. The problem is that programming requires a mode of thinking which is difficult. Lots of people, even people who do it daily, who are trained to do it and exercise great care and use great tool tools, are not great at it. This is not a syntax problem or a lack of decent libraries problem. We have simple programming languages with huge bodies of libraries. What's hard is the actual programming.

fusiongyro··on How supermarkets choose where to open and close
We have the same law here in New Mexico. No booze can be sold at a store until after noon on Sundays.
fusiongyro··on High Sierra's Disk Utility does not recognize unformatted disks
I thought they were sunsetting Airport devices and would be surprised if they kept putting software development into them.
fusiongyro··on [dead]
I'm imagining a glider in Conway's game of life trying to find a bug to exploit. What would that even mean?
fusiongyro··on [dead]
You don't have enough information to conclude anything about the simulator's universe just because they thought of this one. Consider wakamoleguy's argument about Pacman above: Pacman could apply that same logic to conclude our world is like his, but the simulation's rules just don't impose such strong constraints on the simulator.
fusiongyro··on A Map of Native American Tribes
I'm aware of two here in New Mexico, the Pó Restaurant in Pojoaque, and I believe there is a new one in Albuquerque by the Native American Cultural Center. I've eaten at the Pó restaurant about 12 years ago, and it was not a great experience, but I hesitate to hold that against them since it was ages ago; it might have just been a bad night. The other one I haven't tried yet.

My impression as a New Mexican is that the local cuisine has elements of native cuisine (tamales seem more native than enchiladas). But, I also have the impression, perhaps unfairly, that native cuisine was kind of bland. I think Bourdain did an episode where he went onto the big Navajo reservation and they roasted and fed him sheep; I recall they ate basically the entire animal, but I didn't see salt or a spice being put on it. I'm sure every native group is different but around here, there was sheep, corn, squash, beans and not a lot else. Even the chile we're famous for was imported (from California, hilariously).

fusiongyro··on Is Rotten Tomatoes Killing the Movie Industry? No, Bad Movies Are
Novelty is key to entertainment. At some point, having the same three guys show up and fight a villain gets repetitive. The studio likes safe bets because the costs are so high. But you don't get 1977 Star Wars money on things that closely resemble things that came out last year. The movie industry has gone through this kind of cycle before; they enter a very creative few years, and then they go through some greedy lazy years where they try to reissue the things that won a few years ago, tweaked slightly.
fusiongyro··on Programmers who want to change how we code before catastrophe strikes
I feel like this is part of why Brooks says build the first one to throw away, because you're going to.

People seem quite unable to imagine life with a program that doesn't exist. Building a more precise specification would be valuable if people were really able to evaluate the specification as if it were a program, but they don't seem to be able to do that. So we wind up building the whole thing to see if it's right, and it never is, but then we build the next one, and it's much closer.

fusiongyro··on Is Rotten Tomatoes Killing the Movie Industry? No, Bad Movies Are
If those people do, why are the studio executives complaining? Perhaps it's because "Ticket revenue was down at least 12 percent, and ticket sales were at their lowest point for the season in 10 years. Audiences did not want to see remakes of old TV shows (bad news for Baywatch and CHIPS). They did not want to see badly reviewed franchise entries (the take for the latest Transformers installment was way down)."[1] (linked from the article).

[1]: http://www.philly.com/philly/entertainment/movies/dunkirk-gi...

fusiongyro··on JDK 9 General-Availability Release
You can use Jigsaw to deliver smaller self-contained systems. It was never going to make the JDK itself smaller, just (maybe) help life for non-developers who have to use our crap.
fusiongyro··on Bootstrapping Urbit from Ethereum
It's interesting that you want them left out and then, as an aside, bring the parent's into it.
fusiongyro··on Implement Tcl in Tcl (2007)
Even aside from changing the syntax, you often have to do this to modify the resolution strategy, such as using breadth-first instead of depth-first search, or add probabilistic or fuzzy logic. A lot of papers on Prolog from the 80s start with "what would it be like to use logic-X from Prolog?" You can do a lot of interesting deep cuts like this without a huge amount of work. Prolog even has a built-in context-free parser that works the same way: definite clause grammars.
fusiongyro··on GNU Taler
The nice thing about bureaucracy is that it doesn't leave any room for debate. Not everything needs to be debated. If you're on HN, you're here to waste time. The click is free.
fusiongyro··on GNU Taler
Usually if you editorialize the title of the link submission the mods will reset it to the title of the page.
fusiongyro··on The Realities of Being a FOSS Maintainer
There are three lemonade stands. Two of them are giving away free lemonade; the third is giving away a free lecture about why I shouldn't feel so entitled to free lemonade alongside charging me for theirs. Who's really confused about the economics of this situation?
fusiongyro··on Practical File System Design: The Be File System (1999)
The RDBMS stuff about BFS seemed pretty overstated to me; it amounted to something more like arbitrary file metadata plus indexing that metadata. Frankly, the integration with Tracker for media and mail was pretty compelling: Tracker did half the work of XMMS and half the work of the mail application, so the media player just had to play files and do scrubbing and the mail app just had to let you view/edit individual messages. The search/list stuff many apps have was provided by the filesystem+Tracker.

Keep in mind, this was during the era of Microsoft FindFast. FindFast worked by continuously crawling the filesystem, so the extra cost you might be incurring on BFS on-demand was happening in batch mode on Windows at great cost. slocate still works essentially the same way and is widely used on Linux but doesn't really do metadata queries; Beagle and Spotlight do the same thing as FindFast but plug into filesystem notifications to make the reindexing less painful. I don't think it's necessarily an insane idea to make this part of the OS at a lower level, especially in an era when filesystem notifications were kind of a new idea.

As someone who lived through that era, BeOS was always a long-shot. But it was crazy responsive and looked good. I don't think BeOS failed because of technical shortcomings really. BFS was compelling compared to HFS+, FAT32 and ext2 (and it could mount at least FAT and ext2 natively); ext3 and ReiserFS came out around the same time as Be Inc dissolved so journalling was still a significant filesystem differentiator at the time. Whether BFS was relevant to it or not, BeOS had a reputation for being very good at media operations.

fusiongyro··on The Realities of Being a FOSS Maintainer
You miss 100% of shots you make when you aim away from the basket with no ball in your hands too.

There is a market for his product. Nginx and Apache already own that market. His differentiator is being easy to install. Puppet et. al. solve ease-of-use for large corporations with the budget. The niche that cares about being easy to install is the niche with no money and nobody to pawn it off on. That niche is also passionate and loud.

If he could make some money back for his time, he would already have had a business here.

This business idea is essentially selling pre-made cardboard signs to the homeless. If they have the money, they aren't homeless; if they don't, well, they already make their own signs.

fusiongyro··on The Realities of Being a FOSS Maintainer
Of course you're going to hear supportive friendly things from your friends. It's much harder to tell someone a hard truth if you see them as your friend and want the best for them.

Here's a blunt truth. If it's easy for me to ditch your product, your product has no value. 90% of the comments here on HN amounted to "gee, I guess I have to spend an extra 20 minutes configuring Nginx now." Solving 20 minutes of Nginx configuration is not a viable business. System configuration is handled by some Puppet library author. Who's going to spend $100 on your product so they don't have to spend $20 on a non-free SSL certificate?

You're friends with the RethinkDB developers? The moral of their story was even if you have a compelling product, even if you have an interesting niche, even if you give it away for free, even if you give away the source code, even if you have features nobody else has, if you are entering a saturated market you are facing a massive, time-consuming, expensive up-hill battle. Moving away from RethinkDB to Postgres is hard. There are things RethinkDB does that Postgres just doesn't do. But people did this anyway instead of paying, instead of contributing.

Moving away from Caddy is simple. Your product barely even exists. That's why you're having trouble making money. Solve a real problem and you'll make real money.

fusiongyro··on Chelsea Manning: The Dystopia We Signed Up For
How's that different from bad customer service in an earlier era? "I don't know what form you need and my manager is at lunch."
fusiongyro··on Lisp Machine Manual (1984)
Thanks! I really appreciate your sharing this with me.
fusiongyro··on Lisp Machine Manual (1984)
This was hugely useful to me, and I appreciate the copious links. But I am still stuck on something. In the early days, you programmed the home computers with assembler (it was the truth) or you used co-equal non-truth languages like C or Pascal. Later on, the OSes were all written in C, so the application code was being written in C (or mixed C + assembler) and you had FFI problems if you weren't using C. But what happened in between these that caused the OSes to be written in C rather than Pascal? Was Pascal just not perceived to be useful as a systems language?

Politics and Unix would explain it if, people were borrowing and/or aping Unix in their OSes, or if people just generally had the impression that C was more powerful. Is that kind of the direction you're pointing?

fusiongyro··on Lisp Machine Manual (1984)
My comment was directed at the quote about higher-order functions, which is a more legitimately surprising thing than something about scope. And of course we're talking about whatever would have been considered "Lisp" by Appel in 1992, even though you and I might know better and be more precise today.
fusiongyro··on Lisp Machine Manual (1984)
Wow. Well, at one time, maybe Lisp did not have that? It certainly did by the time this book was written though.
fusiongyro··on Lisp Machine Manual (1984)
I thought that the prevalence of Pascal compilers was partly due to p-code as a compiler implementation technique, not that they were generating it.

As I mentioned above, this raises questions about why C came to dominate Pascal. They both had a comparable early foothold on PCs.

fusiongyro··on Lisp Machine Manual (1984)
That erodes part of my argument. Why did C overtake Pascal? If it wasn't performance or availability, was it just preferences? Or portability from other existing codebases?
fusiongyro··on Lisp Machine Manual (1984)
I agree, but just because I'm curious, what did Appel say? Different dialects of Lisp have had different scoping rules, but beyond that I don't know what is true or false. I believe earlier ones were dynamically scoped, because I vaguely recollect that lexical scoping was an important change in Common Lisp and Scheme. Of course Common Lisp has a special way to ask for dynamic scope.
fusiongyro··on Lisp Machine Manual (1984)
> My assertion is that you're looking at the wrong decade for C's network effects. You should be looking at the PDP-11 decade, not the PC decade. And in the PDP-11 decade, I believe there was much wider awareness of Lisp.

This is the crux of it I think, and unfortunately my flashlight isn't bright enough to get much further. I was born in 1981, so this is all reconstruction for me. Unfortunately, the people who were there are getting scarce. Anyway, thanks for talking it through with me!

fusiongyro··on The sudden death and eternal life of Solaris
What was the winning bid? :)
← PreviousPage 8 of 34Next →