Not very pro or anti BASIC but very pro your rationale, and love that you do what you do because it is fun and stimulating. I love reinventing wheels also, and, in fact, believe it is under appreciated just how useful it actually is. I'd encourage people to reinvent things for their own benefit, maybe you might end up building a better version of something, but more importantly you will possibly encourage, energise or inspire another to explore and learn.
This is potentially a inflection point for windows being the dominate OS. If Google, who now have Android working on desktop, and can market it well enough. Since half of the mobile users in world would be less afraid to try something they are familiar with on their phones.
> If Google, who now have Android working on desktop, and can market it well enough
Too little, too late.
Everyone's switching to Linux now, in droves. Microsoft have hit that Trust Thermocline[0] and that has made perfectly ordinary people like your parents or the guy you sometimes chat to in the pub or your plumber go "You know what, fuck it, I'm going to give this Linux thing a go", and they actually are doing that.
We're at a point now where most people do everything in a web browser, for better or worse, so the OS that your browser runs on is pretty much irrelevant. It's been that way for years, but it's taken Windows to get to a point where it's not just that people don't like it but they actively distrust it.
I think the initial surface look makes scheme give a bit of an 'oh crap' response. But since minikanren is actually a small program and scheme doesn't really have syntax the language should be less of a problem than initial concerns might make one think. Grokking the actual logic in any language is going to be the bigger challenge. I guess I am trying to encourage just rolling with lisp if you can, but I totally get the initial reactions toward scheme though.
That's somewhat comforting! But on the other hand, it means also that some of the folk who would be perfectly able to understand the big idea are getting gatekept by just the look of the parentheses, even though host's concrete syntax is of little importance. Which is a darn shame.
Yes, I agree, and understand the point better. Totally a great thing if this can be made accessible to a wider audience and not expect them to do all the work to grok it, especially if there are easy/easier ways to bring it to a wider audience. The parentheses don't usually remain a problem after the initial bump, I had the same issue when I started clojure but after a short while it doesn't continue to be jarring. I think after about 90 minutes it just started to be "natural" perhaps that the wrong word, it was just something that was like ok after a bit and didn't notice too much.
I don't know about other people's experience, but from mine, I see a lot (most) devs abstracting too early in the name of clean code. I guess engineers gonna engineer when simple boring repetition is sufficient and those premature abstraction are unnecessary.
Yea lets build a whole docker setup for this little Sudoku app that never will have more than 100 users. I mean, for fun overengineering small projects can be a great learning experience but for work? Keep it simple, stupid.
(In case it wasn't clear, im agreeing with your point and just giving some example)
> lets build a whole docker setup for this little Sudoku app that never will have more than 100 users.
Looks good on the CV though and managers who hire-by-cv-not-sense love that kind of thing. You'd be amazed at how many interviews I've failed by pointing out that following the latest trends and over-engineering isn't always a good plan.
Also means there's a constant supply of work for contractors who can unpick that kind of gibberish back into reliable systems which is nice.
But do you really want to work at a company with managers that have zero technical experience? To me it always has been extremely annoying working with people that can't imagine the magnitude of work, that some "small" changes come with.
My current boss and company owner is also a programmer and its far easier and good for my nerves. He just doesnt have the time to code anymore.
If I had a penny for every time I try to dissuade a dev from busing a huge k8s system for a business that does not have a single user yet - I would have a bunch of pennies
I work for a Kubernetes Certified Service Provider and I dissuade people as well, it's so anti-climatic when embarking on a k8s journey and then having more pods which are overhead than the actual customer pods.
Yeah but what does simple mean? I struggle with that a lot. In my experience, keeping it simple means not being flexible when requirements change. Adding new features becomes tedious or even a mess. Keeping things simple is an art, certainly not an easy one.
Its extremely easy. Just dont overthink, implement the stuff you gotta implement and move on. Simplicity generates flexibility. Its also easier to refactor if your app isnt a architectural docker mess.
Boring repetition is a bad fit for the human brain. Working memory is very small. Mistakes per line are frequent. It wants to see patterns that are not quite there. Even when it works out, it's millions of times slower than having the computer fill in grunt work from a more concise and readable spec of the problem.
