Hot take: Could font designers please just agree that the only valid way to write 0 for technical fonts is with a dot in the middle? 0-with-nothing is irritatingly ambiguous with O, 0-with-a-slash is irritatingly ambiguous with Ø, and I’ve never seen the 0-with-broken-edges actually used outsize of Brazilian license plates.
Just pulled some statistics from what people download: https://neil.computer/notes/berkeley-mono-font-variant-popularity/
The dotted-zero is indeed the most popular.
Nah, I like my slashed zeros. You just need properly distinguishable characters. Many font designers get it wrong.
Or just let you choose. There were a few things about those fonts that bothered me initially, but with customisation they became my favourites.
I’m at the sad and tired point in my life where I don’t want things where every nuance is customizable, I want things where the defaults are pretty good. :P
What is your opinion on writing a 0 with a backslash, like in Atkinson Hyperlegible?
Never seen it before in practice! I suppose I have no objective complaints. I might worry a little about dyslexic legibility, but no practical experience with it.
Yeah, I agree. my eyes are pretty bad, and I struggle to read code at even 14pt sometimes. I pretty much exclusively use Source Code Pro as my main programming font because it has the most distinctly different letters and the dot-in-the-middle 0 and NO LIGATURES.
I want to try clojure development with emacs.
I’ll be installing and configuring spacemacs with CIDER, then writing a simple web application using the Luminus framework
I run my own mastodon and friendica servers but I want to learn more about ActivityPub. I’m going to start by reading the spec https://www.w3.org/TR/activitypub/
I’ll have to give projector a go. I tried gateway but it was super buggy, to the point where it just didn’t work at all after about 5 minutes.
I want to love IDEs but I’m finding it hard to wean myself off just ssh-ing into a VPS and using vim, which has served me well for quite a while.
VS Code is both. I do all my development in it (both at work and at home) but it’s seemlessly sshing into a server under the covers. The Remote extension is just magic.
The remote extension is too much magic. It SSH’s into the remote machine and then downloads a binary blob of an almost complete VS Code install. This is great for getting your extensions all working but it means that you’re out of luck if you’re targeting a platform that doesn’t have Electron support and official VS Code builds (i.e. almost anything that isn’t x86 Windows/Linux/macOS).
So it seamlessly works so well that you don’t even need to know what’s going on under the covers and it works on all the platforms 99.9999% of development occurs on? :p
I just want to say that ruby isn’t done innovating yet. They just added static typing last year, which is a really big deal. For a language to start out as dynamic and gain optional static typing 20 years later is pretty cool. Also, it may not have a huge following now, but there have been a lot of newer languages created since ruby’s inception and ruby still has enough of a following to get pretty significant updates 20 years later.
lol, and I’m over here still using legal pads for everything I do. Ruled paper is really easy to wireframe on. If you need more than just straight lines across the page, you can tear a page out, turn it 90 degrees and stuff it behind the page your designing on and bam! perfect wireframing grid!
I think in many cases people hate Java, and by extension, hate OOP. Java being the first mainstream OO language, and still the poster child for OO in many minds, gives object-orientation a worse reputation than it would have if there were other OO languages (apart from C#) one could actually earn a living with.
Most people hate the working environments in which Java is used, with their power structure, deskilling of the worker, fordist approach to software development. Wait for Go to become the new Java and they will start projecting the same hate on Go, regardless of the merit of the language design or lack thereof.
You don’t hate OOP, you hate capitalism.
Go is actually explicitly designed for that approach to development.
I know, that’s why I mentioned Go specifically. Give it 10-15 years and all the fanboying will die out.
Huh? I vehemently disagree with this. A language which deskills development enables novice programmers or non-progranmers to build software and systems for themselves with less time investment required. And given that personal software will never see the scale of usage or the sheer variety of deployment conditions that corporate SaaS often sees, personal software doesn’t need to be as correct as corporate SaaS either, so trading performance and correctness for functionality is a very realistic trade-off for personal-use software.
I find these language identity wars to be odious. You don’t like Go, that’s fine. Please don’t extrapolate systemic failures from your own personal likes and dislikes.
are they? this to me is up for debate. The deskilling that comes with these languages is a problem only under a specific mode of production. Being able to split the workload across a bigger group of people, having “protocols” to standardize development, enable less skilled people to write reliable software are not bad things in themselves. They are bad things in our specific economic system.
It’s funny you mention 2015, since around that time, a as new batch of languages appear that aren’t as heavily invested in strict OOP appear. Java and C# only accepted multi-paradigmatic programming once it was proven to be non-threatening by newer languages.
Before that, it was regarded as superfluous and academic.
To be fair Windows 10 does nearly the same thing. If you try to run an exe that isn’t code-signed, you get the “Windows Protected Your PC” alert. and it hides the “run anyway” button unless you click a “more info” link. Code signing is crazy expensive it’s like $500 for only 2 years. And even after buying the code signing cert, you still have to get a minimum number of installs before your exe is really trusted.
I use two TOPS 100 sheet Legal Pads. One is for writing down everything as it happens and the other is for planning and listing what I’ve done. I’ve used this system my entire career, and it’s worked great. Sometimes I confuse one legal pad with the other, but other than that, this has been a great system. Also, since I’ve used this system my entire career, I can look back at my huge stack of legal pads for fun and see what I was working on 5 years ago. It’s kinda cool.
Debugging stored procedures in MSSQL. It took a long time to set it up, and once I had it set up, I still couldn’t see the records in a table variable. If you want that your choices are save it to a new table in the database, or dump the table variable to xml and parse the string.
SET @XMLSTR = (SELECT * FROM @TABLE_VAR FOR XML AUTO)
If the goal is to entice people to switch from twitter to mastodon, making the transition as easy as possible should be the main focus, and so large instances like these are fine. Let people just log in and toot. Let them try it out before getting on my instance and cluttering it up with dead accounts. If they like it and they want to learn more, they will make another account somewhere else. Does anyone have just one mastodon account? I don’t think so.
Lisp is one of those things that I want to like, but every time I think I’ve found a way to actually like it and use it something stops me. Racket is the closest I’ve ever come to using a Lisp-y language for non-trivial code. I really enjoy the community, there are a ton of libraries available, and there’s even Typed Racket! But then I remember that someone else is going to have to read / modify / run my code and they’re likely to be annoyed that I used something relatively obscure, and I back off. So my theory is that Lisp is less popular than many people think it ought to be at time
t simply because it was less popular than many people thought it ought to be at time
Yeah, this is my reasoning for not using Lisp/Clojure at work. I would feel bad for forcing it on someone that has no interest in learning it.
I made the case at Racket Con a few years ago that the way to get adoption is to introduce it in tools that aren’t critical to production, which shows people the power, but allows them to slowly learn what makes it tick. I tried to introduce scribble for my team’s internal documentation afterwards, and failed because $X decided godoc was better. As the codebase is go, it was hard to argue against, even though most of the documentation is not a good fit for godoc.
That’s a great idea, even if it didn’t work in that particular case. Now that I’m thinking about it, I could probably find a way to introduce scribble into my work, thanks!
If you’re looking for boring and battle proven, I would suggest one of these languages: Java, C#, PHP, Python, Ruby, Go, Node.js or Erlang. I’ve had a hard time with web frameworks that aren’t in those languages. It’s not that I don’t understand them, just that I wasn’t as productive.
This is some excellent “Code Golf”, but I would never write C# in this style. I’m pretty impressed that C# now has the functionality for pattern matching on tuple values though.
I don’t understand this post at all. Who has not been using SQL in some capacity, somewhere? SQL has been pervasive in application development since forever, and is an essential skill, even for non-developers like business analysts. Even when “NoSQL” was the hot new tech everyone talked about, people were still using SQL somewhere in their stack, often for reporting or analytics.
I’m beginning to get the impression that there’s a new generation of developers who actually haven’t been exposed to SQL that much - the last five years have seen plenty of boot camps that teach MongoDB or similar instead of a relational database.
This is correct. I’ve interviewed several people that only know Active Record or Entity Framework and they struggle doing simple joins/aggregations directly in SQL. They know everything about their ORM of choice, migrations, backups and deployments, but that’s all they know. And to be fair, for smaller projects that’s all you need to know.
And I would say that the corollary to that is older developers like myself who got exposed to NoSQL databases in their early days of immaturity and frequent reliability issues. It was an eye opener when I met a group of young developers who perceived MongoDB as this timeless, essential, and totally reliable piece of infrastructure.
I mean, they are not wrong. MongoDB is reliable these days.