Ycros

On lower dpi monitors I use bitmap fonts with no smoothing for coding, they are crisp. See http://upperbounds.net/index.php?menu=download for a bunch of these fonts (I use Proggy Clean with slashed zeroes and bold punctuation). Note that you may have to play with your font size and turn off any antialiasing in your editor to get it looking right.

I used to use an Ergodox Infinity that I built from a kit. Since then I've moved to the Model 01 from https://keyboard.io

Why? I find the thumb clusters way better, I feel like they're just a bit too far away on the ergodox keyboards. That, and the shape of the keys and the curve of the stagger are better IMO.

The downside is you can't use any keycaps because they're unique to this keyboard.

Ah, nice to see I'm not the only one running youtube-dl on a phone via Termux.

The popup dialog you get when you click either "like" or "dislike" is annoying - show it the first time and then don't show it again. I'm happy to scroll through a bunch of logos and quickly mark some likes/dislikes, but not with a popup on each one.

Good stuff. It looks like they've addressed a few of the ergonomic issues in their language with this release. The old way of doing iteration and having to use string interpolations just to reference variables were annoying.

Upon reading the headline I had assumed this had something to do with the ELK embedded operating system, it doesn't. Maybe not a good idea to pick the same name as another product already in the embedded space?

this just went from cool toy to really useful

I give Firefox a chance every few months, and even after all their work I still feel like it has occasional performance issues and I end up right back in Chrome.

Just a warning that this is one of the modules that's licensed under the controversial "Apache 2.0 with Commons Clause" license.

I originally bought an iPad just for music stuff, but a lot of the time I'm hooking it up to an external audio interface for better quality IO and midi. I think that iOS' support for USB Audio and USB Midi devices is also a large part of what helped it build an ecosystem of decent music making apps.

I agree that not having a headphone jack combined with the unacceptable latency of bluetooth makes it unusable for on-the-go music making.

As for pricing, I think that won't change on Android. Music making is a niche market, and these apps are not cheap to develop.

Unfortunately you can't use these APIs to create third party clients because that violates their ToS, they are meant only for writing bots. If they catch you using these APIs with your full account credentials they'll ban your account.

I think it's ambiguous enough that this in itself will drive people away.

I've gone down a similar line of thinking when writing a lot of SQL over timeseries or otherwise ordered datasets recently. Going in a more functional and composable direction while keeping it limited so that hopefully the query execution engine can still make good optimizations seems like the right idea.

Making it a separate and open language outside of Influx is also a great approach - I'd love to see other databases try adopting this. I'll definitely be keeping an eye on this project.

I'd expect the "What's New" section to tell me at a high level what's actually new in this release.

I don't agree, it clearly fits the definition.

2.0 added an exclamation mark (!) postfix operator that asserts a type as being non-null/non-undefined. So these checks are easy to explicitly ignore.

Just give me a clean and simple way to sort my subscribed channels into groups, but also being able to group by title - some channels post a bunch of varied stuff all on the same channel and I find it annoying to keep track of the specific things I care about.

There's nothing there for any phones to connect to...

Can you elaborate on what you mean by that? 1.7 added 'this' typing improvements, and it looks like 1.8 is adding 'this'-based type guards.

I don't agree that VS is ahead of the competition. In my view the best IDEs in the Python space are PyCharm and WingIDE, and they've both been doing excellent auto-complete, debugging, refactoring, etc. for years.

That said, I'll probably try it out.

This is what I want out of a CMS, I want it to be something I can add into an app, not something that wants me to write my app around it.

The first thing that grabbed me about bazqux was just how fast and responsive it felt to use. The second thing was that it was the closest replacement to Google Reader I had come across. I'm still using it.

I'd love to see some improvements done around their plain old text based diffs, and merging.

C#'s functional side is why I actually really enjoy working with it. I get to use a nice blend of OO and functional, where each makes sense. OO more on a macro scale, organising code.

On Windows, I use Scoop http://scoop.sh/ (vaguely similar to homebrew on OSX). There's a Rust package which will install all the dependencies for you. It hasn't been bumped to 0.9 yet, but I assume that'll happen soon.

I'm finding that my OO code style these days is very composition heavy with pretty much no inheritance use. I think given Rust's type system, I'm not going to miss inheritance much.

In our project we've ended up with our controller code being defined outside of the .controller call (we're using TypeScript, and someone wanted to use the class syntax). This means that our controllers are accessible directly, and for a unit test, they're just functions we can call.

So we just pass our own mocks in, it's much simpler than trying to use Angular's injector mechanism.

That is an incredibly well written announcement.

[Other] Bazqux - https://bazqux.com/

Are you saying you test in other platforms, just not AngularJS? Or is your question actually about the value of automated testing of code in general?

A strong point in AngularJS's favour when a bunch of my coworkers were evaluating different frameworks was that it was designed with testing in mind: dependency injection as a pervasive feature is huge for us, because that's what we've been doing on the server side (C#) for a long time. Angular seems to be encouraging its users to modularise code more, and that's a good thing.

We have fairly comprehensive test coverage of our JS code, this is pretty easy if you take the happy default path of Karma and Jasmine. From my point of view, we've always had comprehensive server side testing, now that a lot of logic has shifted to the client and sits on top of a much lighter-weight API on the backend. All that JS code needs to be tested.

Apart from lower level unit testing, we also have integration tests which drive real browsers through our apps. This is pretty important to make sure the whole thing including the server side code works together properly. These gain immense value as the project grows in size and complexity.