bbbobbb (u/bbbobbb) - Readit News

bbbobbb commented on Don't Download Apps blog.calebjay.com/posts/d... · Posted by u/speckx

dwedge · 23 days ago

> Sometime in the next 5 years, someone will be forced into arbitration with Uber after being hit by one of their self driving cars

I got hit by an Uber when crossing the road last year. I reported it to Uber who said publicly "oh that's terrible and not ok, DM us" and then completely ignored me.

bbbobbb · 22 days ago

Is there no police where you're from? Why are you reporting supposed hit and run to tech support of an app?

bbbobbb commented on Seven Days at the Bin Store defector.com/seven-days-a... · Posted by u/zdw

tra3 · 7 months ago

Am I the only one that feels uncomfortable returning stuff? Took me years to get to get over, and yet I'd still prefer to forego buying something rather than returning it..

bbbobbb · 6 months ago

I don't recall ever returning anything. I don't buy that much stuff in general, but I feel like having the ability to just buy and return stuff makes you end up with more junk.

bbbobbb commented on Boring tech is mature, not old rubenerd.com/boring-tech-... · Posted by u/mikece

steveBK123 · 10 months ago

Exactly - This is known to graybeards and mostly ignored by the youths.

We've seen the wheel re-invented many times and would prefer to work on something other than the wheel again. Stuff like solving user problems and making money.

Meanwhile you have the coworker who uses some new but soon to be deprecated language/framework on every project, leaving a field of unsupportable debris in their wake..

bbbobbb · 10 months ago

It's often ignored because not all people get to work on interesting new features or care about the customers. This is all cool and dandy if you're a founder or working a job where the actual product is interesting, but most jobs are boring with no actual incentive or even a way how to care about the customer and then making it at least technically interesting in some aspect is a way not to go insane.

Just playing the devil's advocate here. I would prefer using boring technology that gets the boring work done as quickly and easily as possible anyways, but that's because I have more fun doing other things than working.

bbbobbb commented on My Unhealthy Relationship with Keyboards jackevansevo.github.io/my... · Posted by u/jandeboevrie

Jackevansevo · 2 years ago

Plugging in the USB-C cable is for charging only, so it would still be a wireless connection. I'd still need to connect via bluetooth or the Logitech dongle. I won't get any of the benefits i.e. latency / lower power consumption of using a wired connection.

I also have concerns about the charger degrading the battery if it's completely plugged in.

bbbobbb · 2 years ago

Right, I only meant in regard of inconvenience of having to charge it.

bbbobbb commented on My Unhealthy Relationship with Keyboards jackevansevo.github.io/my... · Posted by u/jandeboevrie

bbbobbb · 2 years ago

While I prefer wired keyboard as well (due to not having to deal with pairing / connection issues), this argument I don't understand:

> Firstly the board is completely wireless, which means I have to charge it via USB-C. As I'm sat practically tethered to my desk all day a permanently wired option would actually be more convenient as it would save me to the hassle of charging.

Then plug the USB-C cable in permanently? How is it different from it having a wired keyboard?

bbbobbb commented on The joys of maintenance programming (2011) typicalprogrammer.com/the... · Posted by u/pramodbiligiri

jckahn · 2 years ago

Agreed. Imagine you’re a CEO: Why on earth would you want your expensive engineers reworking something that already makes money? It seems much more sensible to leave the working code alone and focus on new revenue-generating opportunities.

bbbobbb · 2 years ago

That's not what the post is about. They describe the process as mostly fixing issues with existing software, so the motivation is that something is broken or not working as required anymore.

Refactoring it is just one of possible parts of the process, much opposed to 'yeah this legacy code is broken dogshit and needs to be rewritten even though the current software is already written, proven and works for 99% of the stuff we need' approach.

bbbobbb commented on Why are our keyboard not wireless? zsa.io/wireless/... · Posted by u/yla92

throwaway743 · 2 years ago

Not sure about keyboards, but Logitech mx3 mouse is great and only needs to be charged like once a month after using it nearly all day every day. Also super ergonomic and works on any surface

bbbobbb · 2 years ago

It also works just while plugged in so there is no downtime. I feel like I charge it couple times a year by any random usb-c that is on my table at the moment while I keep using it. Even if it didn't, it takes maybe 1-2 minutes to charge for the rest of the day so there is no disruption.

bbbobbb commented on Why the IDE needs to be reimagined codestory.ai/blog/reimagi... · Posted by u/skp1995

bbbobbb · 2 years ago

I'll just have to guess the reimagined IDE is not longer very text-centric given that without proprietary JavaScript the page is just a green background.

bbbobbb commented on PicoLisp Tutorials picolisp-explored.com... · Posted by u/damir

DonaldFisk · 2 years ago

The problem with Lisp is that there are different dialects, and if you program in more than one, you need to be aware of the differences between them. It would be nice to be able to switch between them on different projects without being caught out by their differences before getting used to the other dialect, or having to context-switch. It would also be nice to port programs from one dialect to another without major editing. But Picolisp is another dialect, which on the surface is quite different from Common Lisp and Scheme/Racket and, I assume, Clojure. If you want to keep your Lisp implementation small, why not just implement a subset of Common Lisp, or build/use a Scheme variant?

bbbobbb · 2 years ago

This only sounds like a 'problem' because the lisp dialects are so similar that you would almost expect them to be the same, no?

That seems like a nice feature - you know Common Lisp so you have to only learn some nuances to write PicoLisp effectively.

When it comes to the c-family of languages, you wouldn't expect a complaint about having to be aware of the differences between C and JavaScript since you can't even entertain the idea that they are all that similar.