Matt RaibleMatt Raible is a Java Champion and Developer Advocate at Okta. developer.okta.com

The JHipster Mini-Book The JHipster Mini-Book is a guide to getting started with hip technologies today: Angular, Bootstrap, and Spring Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.

This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.

For book updates, follow @jhipster-book on Twitter.

10+ YEARS


Over 10 years ago, I wrote my first blog post. Since then, I've authored books, had kids, traveled the world, found Trish and blogged about it all.

Bandwidth Speed Issues

In the last few days, I started to notice a huge slowdown on my MacBook Pro when surfing the net. At first, it seemed to be a Firefox-hogging-a-shitload-of-memory issue. So I started using Safari instead. After a few hours of using Safari, the problem came back and pages were taking 5-6 seconds to load. I have a Cable (Comcast) modem, so I didn't suspect any bandwidth issues.

Last night, I got tired of waiting and decided to do some further investigation. I started off by running several bandwidth speed tests. All of them reported similar statistics: download speeds of under 300K/sec. I called Comcast, they ran some tests and determined that there were no package loss issues between my modem and their facilities.

Since I moved my modem downstairs last year, I tried moving it upstairs. Same result. I tried plugging it directly into my desktop and voila! - 3MB/sec. I have 2 NetGear routers setup (one for each laptop since my MacBook Pro's wireless abilities suck) and it seems like they are the source of the problem. Do routers go bad like this?

I'm considering buying an Airport Extreme to solve all my Mac-related wireless issues. Unfortunately, it only has 3 ethernet ports and I'd prefer a lot more.

Posted in General at Jan 24 2007, 01:02:24 PM MST 11 Comments

java.blogs - nice crippling update

I like how java.blogs updated their site the night before last. The changes seem to be cosmetic for the most part, with a cleaner look n' feel and some language features as well. Seeing these updates is good, and based on the update last week (where they forgot to find.replace ${community.name} with "java.blogs"), it looks like Atlassian might be releasing the software behind java.blogs.

However, there's one thing they screwed up in their most recent update: the software ceases to function.

Ever since they updated, no new feed entries have shown up on the first page. You can tell because the last entries added are experiencing record hit numbers. WTF Atlassian? Did you update the software and forget to test that it works? ;-)

java.blogs' lack of updates

In reality, I can't be too upset. This lack of updates is boosting my productivity.

Posted in Java at Jan 24 2007, 11:56:02 AM MST 6 Comments