This was the major problem with the Mac version too. Esc is such a necessary button and they put it behind a bunch of ridiculous other stuff, like if you open the volume slider, now you have to press off of it and then hit esc, so esc is now two button presses.

Yeah anyone who used Skype at the time immediately knew what went wrong

Here’s the thing I’ve discovered over the past two months. You can block every keyword you can think of involving politics and you will still be subject to them in memes that don’t happen to mention the keywords, comments where the blocking isn’t effective, and friends and spouses mentioning them, if not more. Politics pop up in every context. Video game YouTube, programming subjects on hacker news, pretty much every single subject at this point in time is inundated with politics.

For a long time I was the most informed person in my social circle. I can’t deal with it anymore. I blocked every mention I could think of and yet I still think I’m just as informed as everyone else in my circle, at least to a certain extent.

You can’t avoid it. So block everything and you’ll still be informed.

I literally didn’t mention micro services at all. So once again it’s very clear you didn’t read what I wrote. And no, that’s not what micro services are. Smdh.

And now you switch to Firefox. The better browser for years at this point.

pretty sure they’re saying waterfall for building a rocket because that’s literally how NASA builds a rocket, including the software. It’s terrible for building anything other than a rocket though, because the stakes aren’t high for most other projects, at least not in the way that a critical mistake will be incredibly bad.

Because I clearly said that you don’t cut up things into tiny pieces. It was both in the first paragraph in my post and the last one. I said you use tiny functions to glue together larger systems. So yeah you clearly didn’t read what I wrote.

You didn’t read what I wrote at all.

You can write your glue nano-service in c/c++ if you want, it’s just that: glue. It doesn’t matter as long as you don’t need to change the original services which also can be written in whatever you want. Ruby, Python, JS just work out of the box with aws lambda and you don’t really have to maintain them or any sort of build infra so it allows for very little maintenance or upkeep cost. You don’t really test these glue lambdas either.

we’ve been using nano-services for the past 6 months or so. Two different reasons. A codebase we absorbed when a different team was dissolved had a bunch of them, all part of AWS AppSync functions. I hate it. It’s incredibly hard to parse and understand what is going on because every single thing is a single function and they all call each other in different ways. Very confusing.

But the second way we implemented ourselves and it’s going very well. We started using AWS Step Functions and it allows building very decoupled systems by piecing together much larger pieces. It’s honestly a joy to use and incredibly easy to debug. Hardest part is testing, but once it’s working it seems very stable. But sometimes you need to do something to transform data to piece together these larger systems. That’s where ‘nano-services’ come in. Essentially they’re just small ruby, python, js lambdas that are stuck into the middle of a step function flow in order to do more complex data transformation to pass it to the next node in the flow. When I say small I mean one of the functions we have is just this

def handler(event:, context:)
  if event['errorType']
    clazz = Object.const_set event['errorType'], Class.new(StandardError)
    raise clazz.new.exception, event['errorMessage']
  end
  event
end

to map a service that doesn’t fail with a 4xx http code to one that does fail with a 4xx http code.

You could argue this is a complete waste of resources, but it allows us to keep using that other service without any modifications. All the other services that depend on that service that maps its own error types can keep working the way they want. And if we ever do update that service and all its dependencies, now ‘fixing’ the workflow is literally as simple as just deleting the node and the ‘nano-service’ to go along with it.

I should note that the article is about the first thing I discussed, the terrible codebase. Please don’t use nano-services like that, it’s literally one of the worst codebases I’ve ever touched and no joke, it’s less than 2 years old.

I’m confused what you’re asking. Google opens sourced the pebble code, which they acquired from their purchase of Fitbit, who acquired it when they purchased pebble. Repebble is an open source project that has been trying to keep the original pebble watches working since Fitbit shut pebble down.

Debugging a Mac is just as simple as debugging a Linux OS… because it is Linux.