My mother is a happy Chromebook user. I’m a less than a happy Chromebook purchaser at the moment. Why you ask? Here’s my history
- 2012 – first laptop. This was a second generation model (the first ever Chromebooks were in 2011. I waited a year to see if they would have legs. It end of life’d for security updates earlier this year (or 2018; I forget). Not bad.
- 2014 – The first Chromebooks with built in 4G were released. I thought this would be good as she’d have 4G. It was. At first. Then we realized you have to be on wifi to get updates so I gave her an AT&T wifi hotspot instead. This computer hit end of life for updates this year. Luckily, it happened after the computer was in my possession and not hers. She wanted to replace it because computers age. No problem. Five years is a good amount of time for an inexpensive device.
- 2019 – I picked the Acer Chromebook 15 (CB3-532). It end of life’s in August 2021. That means we only have two years before that machine can no longer get updates.
- 2021 – I get to involuntary bug a new Chromebook.
I learned today that Google has an automatic end of life policy. It says you can’t get updates after 6.5 years from when the hardware is first released. So I only get two years of updates because the model of computer has existed for four years. I didn’t know this when I bought the machine. If I did, I would have sat there looking up the end of life dates for every model at Best Buy.
Granted the computer only costs $240. But there is a cost to setting up a new computer when you don’t live near it. One that I’d like to minimize.
Oh and the reason I was looking at the in the first place? Amazon Music is no longer working properly. I can’t tell yet if it is the war Amazon and Google are having or something more mundane.
There have been a number of changes to Toastmasters Pathways in 2019. This is one of the benefits of an electronic program.
- The Engaging Humor path is new. I’ve updated the Presentation comparing paths to include it.
- The “Reflect on your Path” project is no longer part of level 5. It is now a separate “Path Completion” level. This means that level 5 is now one required project and one elective.
- You can now both view and give speeches in any order. This is great news. It makes the 90 day option to change a path useful as you can browse. (Just don’t mark any projects complete until you are sure you want the path.) Additionally, you can give a “later” speech to work on a skill you need now.
A Cloud-Native Dev is Eating my Cheese! (How to get it back?)
Speakers: Eder Ignatowic & Alex Porcelli
For more blog posts, see The Oracle Code One table of contents
Requirements for Cloud Native
- Microservices scenarios
- Java tools and frameworks not optimized for cold starts and low memory consumptions
- We pre-fetch a lot in memory
- New developers perspective
- Java developers need a lot of RAM on laptop
- 199x – early adopters – Java cool, big/reliable servers, app servers, app always up, JVM optimized for the long run
- 200x – majority, cloud computing, commodity hardware. expect failure
- 201x – late majority
- 199x – Virtualization – hypervisor, app servers as best practice (JavaEE). Tomcat/Jetty as outliers
- 200x – Containers – Microservices, Docker, SpringBoot, go/node as outliners
- 201x – Orchestration – Microservices maturity, Kubernetes, Go/node skyrocketing, Operator/Service Mesh as outliner.
Advantages of Java
- Microprofile standard
- Lots of libraries
- Tons of developers
- Java EE standards + NodeJS Dev experience (no restart)
- Size of a Go binary
- Can use GraalVM
- Build automation tool
- Based on Drools
- Used VS Code
- Showed Kognito business rule – uses custom DSL
It was fine, but not what I expected. My brain was full before I walked in so seeing a demo was hard. I’d seen a Quarkus demo recently. It’s still cool. (I left early and missed the end)