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

The Angular Mini-Book The Angular Mini-Book is a guide to getting started with Angular. You'll learn how to develop a bare-bones application, test it, and deploy it. Then you'll move on to adding Bootstrap, Angular Material, continuous integration, and authentication.

Spring Boot is a popular framework for building REST APIs. You'll learn how to integrate Angular with Spring Boot and use security best practices like HTTPS and a content security policy.

For book updates, follow @angular_book on Twitter.

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.


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.

.NET's built-in tools and controls generate invalid XHTML and CSS

Mails we've received, forum discussions, and recent Splorp posts all complain that .NET's built-in tools and controls generate invalid XHTML and CSS. The workaround? Don't use the built-in tools and controls. The value of .NET without those built-in tools and controls? Not much.

.NET is Microsoft's platform for web services. It derives it power from XML, a web standard. A product based on one open standard should support others, not break them.

When Microsoft does the wrong thing, developers feel helpless. You are not helpless. You have a choice of development platforms. [Zeldman]

(emphasis mine) The choice is simple, use J2EE ~ where the flexibility is free! wink

Posted in Java at Jun 20 2003, 01:14:42 PM MDT 3 Comments

My background is with J2EE. All things being equal, I'd use J2EE over .NET every single time. However, the one thing that .NET has is Visual Studio .NET. Being able to drag and drop components that generate ASP.NET (with code behind) is not particularly useful for me, but it is for a different class of developer (the "corporate developer" often discussed at this year's JavaOne). Unfortunately, the J2EE IDE vendors are simply not there yet.

Posted by Ted on June 20, 2003 at 02:25 PM MDT #

Obviously Ted has not used java code genrationtools yet such as xdoclet and etc..and to be blunt lets not repeat Sun's msitake in code generation by visual tools tha tproduces code tha tyou cannot edit as evident in SuneoNe studio GUI designer! But the strength in choosing J2ee for web services is that you have achoice of vendors for those web services libraries and thus make an informed choice of who matches the standards closer than anyone else!

Posted by Fred Grott on June 20, 2003 at 03:41 PM MDT #

> You have a choice of development platforms.

Sometimes you don't have a choice. I, like Zeldman, am a front-end guy working with back-end coders. The technology decisions behind the devlopment platform have already been made and laid down. My job is to work with that choice, not fight against it because it doesn't do this or doesn't do that. If the development platform decision had been up to me (and providing I actually had enough application background to make such a decision) I probably have chosen differently. That isn't the case, so my goals have changed. I want to find a way to make the current .Net system more compliant. Maybe not perfect, but more compliant.

Thanks for the mention, regardless. Cheers.

Posted by Grant Hutchinson on June 23, 2003 at 02:28 PM MDT #

Post a Comment:
  • HTML Syntax: Allowed