Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Blade: a Java Web Framework

github.com

Post reply on HN
Print view View original

41–50 of 61 posts

Re: Blade: a Java Web Framework

#41

Post by shadowfox »

cryptos wrote: post #18

I'm a bit tired of these sinatra like web frameworks these days. Repetitive url patterns are not that elegant. Why not simply building the API around the fundamental REST concept, the resource? And what about proper content negotiation? JAX-RS has a nice API without much boilerplate and it is more powerful than most "micro web frameworks".

> JAX-RS has a nice API without much boilerplate and it is more powerful than most "micro web frameworks".

This is true. But it is usually much more intimidating for people starting out though. What the micro-frameworks offer is a quick turnaround time.

Re: Blade: a Java Web Framework

#42

Post by dangoldin »

sscarduzio wrote: post #14

No offence, but this is basically the poor man's Finagle. Except Finagle is Netty based, and this is Jetty based. Anyway, this API is really as terse as one can get with Java. Great developer-UX job!

That's the first thing I looked at - whether these were Netty based. We've been using raw Netty for our core application and it's been amazing.

Re: Blade: a Java Web Framework

#43

Post by haylem »

reactor wrote: post #3

Looks like simpler Java frameworks are on the rise now ( http://www.pippo.ro/ , http://sparkjava.com/ , http://www.rapidoid.org/ )

I'm not sure I would consider it on the rise or a recent trend, considering we had a all sorts of these things over the past 6-7 years already (and more, if you include other JVM languages in the mix).

It sure is nice to see a bit of competition though. But I'm a bit afraid of too much fragmentation and proliferation, when sometimes fixing or improving good frameworks might be time better spent. It was (and still is) a bit annoying when every week brings about a dozen new web frameworks, a new UI toolkit, a new stack acronym, etc...

Oh well... I guess you can't really tell what's time well spent, and you can't really product how frameworks will compete and improve evolutionarily.

Re: Blade: a Java Web Framework

#44

Post by iso8859-1 »

garrettgrimsley wrote: post #36
moondowner wrote: post #13

Earlier quoted context omitted.

You can add this one to the list: http://www.takes.org/

As well as Jodd [0], Play [1] and many more [2, 3]. [0] http://jodd.org/ [1] https://www.playframework.com/ [2] http://www.gajotres.net/best-available-java-restful-micro-fr... [3] http://www.javaworld.com/article/2995526/developer-tools-ide...

Play is not minimalistic like Jodd, Spark, Rapidoid, Pippo, Take (that is the name even though the domain name is takes.org) are.

Re: Blade: a Java Web Framework

#45

Post by edem »

hyperpallium wrote: post #40
edem wrote: post #30

Earlier quoted context omitted.

About time. Since the advent of java 8 the platform is rejuvenating. This is clearly an example of that.

Is it? You could write a sinatra-like microframework in java a long time ago (I did). Just use methods instead of lambdas. Though, perhaps 8 has inspired framework developers, and - more importantly! - attracted a more adventurous userbase?

At least I feel like. 8 brought some really needed upgrades (for example we have a new form of multiple inheritance). It is not perfect but I think with the Stream api and the lambdas they simplified things enough for people to at least give it a try.

Re: Blade: a Java Web Framework

#46

Post by frostmatthew »

hyperpallium wrote: post #40
edem wrote: post #30

Earlier quoted context omitted.

About time. Since the advent of java 8 the platform is rejuvenating. This is clearly an example of that.

Is it? You could write a sinatra-like microframework in java a long time ago (I did). Just use methods instead of lambdas. Though, perhaps 8 has inspired framework developers, and - more importantly! - attracted a more adventurous userbase?

> attracted a more adventurous userbase?

That statement seems accurate without "a more adventurous" - I think with Java 8 more people are using Java because they want to instead of because they have to.

e.g. professionally I've used Java more than any other language, it's hands down the language I'm most familiar/comfortable with, yet when I start a side project for myself I've never considered using Java (usually using Ruby or Scala). With Java 8 removing many warts and bringing in a lot of great improvements I'd actually consider using it for a side project.

Re: Blade: a Java Web Framework

#47

Post by xaduha »

cryptos wrote: post #18

I'm a bit tired of these sinatra like web frameworks these days. Repetitive url patterns are not that elegant. Why not simply building the API around the fundamental REST concept, the resource? And what about proper content negotiation? JAX-RS has a nice API without much boilerplate and it is more powerful than most "micro web frameworks".

JAX-RS is just a specification, but implementations of it are not that fast, compared to other Java frameworks.

Re: Blade: a Java Web Framework

#49

Post by atomashpolskiy »

gd78 wrote: post #22

Could someone please explain me where the benefit is over using some embedded tomcat/jetty, weld, jersey, hibernate/jdbc? Setting up such a project cost me 30 min and gives me full flexibility choosing the stack I need for my project.

Speaking from my experience, benefit accumulates with the increasing number of applications under your authority, esp. in case each of these applications is some variation of CRUD Web Forms / Report Generation / Data Processing & Migration (read: typical enterprise environment) and shares most of its' dependencies with other applications, while still having a unique configuration.

In such environment, having the means to create a vanilla project configuration and then extend/customize it a tiny bit for each app is immensely helpful.

Now, of course, this can be achieved without bootstrapping frameworks, but the real game-changing feature is that you get a single "executable jar" artifact for deployment:

- VERY convenient and straightforward to use with containers such as Docker

- if you don't use Docker, 100 jars are still easier to maintain than, say, a cluster of 100 Jetty instances

- possible to use CLI commands to run short-living daemon jobs; no need for a separate job infrastructure (schedulers, triggers, executors and such), just use shell & cron

Besides that you usually get:

- pre-packaged health-check and monitoring tools

- if bootstrapping framework is popular enough: community support for plug-and-play modules/plugins that leverage some particular framework/technology (e.g. Bootique framework is an excellent example of modular approach: https://github.com/nhl/bootique)

Post reply on HN