sping @ sping @lemmy.sdf.org

Posts

0

Comments

243

Joined

2 yr. ago

Boston area. It's far from perfect here, but has been improving rapidly. Cambridge and Somerville especially, which are part of the contiguous urban area. I've had bicycle congestion at some intersections, with ~30 other bikes at a light. Downtown Boston has many fewer riders but a fair number.

My 7 mile commute is about 75% segregated paths, most of the rest in a lane beside motor traffic.

Unfortunately the general Boston ethos is that rules are a curiosity, not given much thought, even when formulating them. So riding the segregated lanes is a frustrating exercise in avoiding pedestrians who are allergic to the footpaths, drivers turning across you into drives and side streets, etc.. A lot of drivers don't even believe that they are supposed to yield when crossing a bike lane and will even argue things like "I had a green light [therefore I didn't have to yield when turning across your path even though you also had a green light]"

The biggest irony is it's often told by vim fanboys, who apparently don't realize a very comprehensive emulator of vim it is one of the editors Emacs offers. But mostly it seems to be told by people who don't even know what Emacs is, they just know they're meant to disapprove of it.

20 minutes to drive to work on a route that would take three hours by bike

Uphill both ways? 3 hours riding is 36 miles if you're taking it very slow.

Entirely depends where. I'm my US city cycling is by far the fastest and most inexpensive transportation option and the whole route is bike lanes and paths. The very best traffic day would be as fast by car but that never happens and would cost me more than $500/month. Train takes 70% longer.

Drag is proportional to the square of speed. Driving fast is very inefficient.

Highway is just another word for a road between places, and interstate is obviously a term local to the few countries that have states and name motorways accordingly. It's that more than one country? Motorway is the more international term.

Yes, 1-2% of American stop signs should stay.

Cringey boomer-esque guy doesn't understand the esque suffix.

I'd call that an IDE, but also one that makes using a non-IDE editor superfluous.

I thought that was just their term for code aware features like jumping to defn/references, doc popups, completions, renaming and so on. That is in no way unique to vscode.

I feel like I'm getting more and more on a limb using Linux as a dev. I'm working on a Linux only product and yet I'm the only one not on OS X and all the rest of them have to jump through hoops to get things to work, and can't run our system locally like I can. My last job was the same except 2 of us used Linux.

I can't even work out what they're getting out of it apart from the hardware. But when I tell them that developing from Linux is easy and comfortable they don't believe me.

Not just Roku, also Hulu elsewhere. Actually I think that's the only place I see it.

Plus most desktops default to a needlessly fat dock/launcher at the bottom.

Yep. The primary advantage of keyboard control. It stops being something you engage your conscious brain for.

Emacs includes vim though. So what would it need to include to have a good text editor of vim isn't it?

I am just regurgitating one of my favorite Perl jokes for a laugh. Though for me the joke contains some truth. Most of the Perl code I've ever seen is pretty impenetrable for non-Perl programmers. I quite literally have returned to my own Perl efforts after just a couple of weeks and had some trouble working out what the code is doing (in ways I do not experience with other languages).

When Python was trying to unseat Perl, that in my view was reason alone to prefer it: I didn't know Python but I could read Python. Though at that point Perl had the benefit of loads of libraries and ubiquity, and Python hadn't got there yet. But it was enough to have me cheering for Python's success at the expense of Perl. I get that Perl has many virtues, but they're nullified by the ugliness and relative inaccessibility of its code in my eyes.

I really hate the magic side-effect variables where you do a pattern match or something and then various obtusely named variables have meaningful values with relation to the last match. To me that's just flat out bad coding, and it's built into the language.

The above was my second-favorite Perl joke. My favorite being:

Perl is the vise-grips of programming languages. It's a tool that can do most jobs, and it's the wrong tool for all of them.

BrEng: mole-grips

Yes, as long as you just type annotation and checker-clean code.

Asyncio programming is a delight, context-based constructs can make sophisticated code safe, robust, and clear. Anything mildly popular you want to interface with probably has a library... There are major advantages to swimming in the mainstream.

Yes it may have grubby and suboptimal corners, but in the real world, making things happen, problems are easy to avoid usually.

Perl is a write-only language.

It was some hacked-together sound output that was terrible quality compared to a real sound card output, AFAIK. You could make it make sounds, but if you care at all about quality it was a non-starter, which is one reason a whole lot of audio hats exist.

Outdated?