Hacker News new | past | comments | ask | show | jobs | submit | puppetmaster30's comments login

I have one. Here is my next one: https://system76.com/cart/configure/lemu8


I wish they went better than 1080p screen. Everything else seems to be on point, including price.


If System76 would support straight Debian stable, I'd be a customer for life. I actively dislike Ubuntu, and think that supporting Debian will result in 'free' Ubuntu support, while not being noticeably more expensive to begin with.


Whoo. It has VGA output.


Yeah, but from career politicians POV: we want liberal arts. STEM or trade skills.... that is risky. They may want a smaller gov. So no way politics will go this way. For example, the Dirty Jobs guy? His video is banned by Google. True.


Any source on Dirty Jobs dude and Google ban? Never heard about it.



> The gist of my argument goes like this: > 1) Passion is a critical component of job satisfaction and overall happiness. However...

> 2) Just because you’re passionate about something, doesn’t mean you won’t suck at it. Which means...

> 3) Following your passion doesn’t always lead to lasting happiness or true job satisfaction. Ergo, my advice to graduates is...

> 4) "NEVER follow your passion, but ALWAYS bring it with you."

It's a shame it was censored. I could have used that advice. I've been considering a career transition into the trades, anyway.


You have a lot of imagination.


I think this is for people that had issues w/ 'jar hell'. I did not.


The biggest pain for me was that it felt like there was no good way to create a library with some internal structure in the form of packages without exposing parts of your internal implementation as public.

When Jigsaw was delayed I was playing with the idea to create a project called shitty-jigsaw, which would just merge all of the packages in a module and change the access modifiers to be more restrictive according to some module definition.


Would shading have done the job? Not to say that's a _good way_, but it _is_ a way.


Sure you can use shading to move everything you don't want in your public API into some other package, or you can use something like ProGuard to obfuscate everything but your intentional public API. However those things will still be public.

The only way to not have those things visible for the user of your library is to only use one package in your implementation.


It's really good for encapsulation and you can do services without dependency injection frameworks


Could you please elaborate, what kind of design you're referring to, here? What dependency injection do you see so vastly changing, here?


I hope Java 9 Module System moves to Java EE.


This brings up some very good points, front end development needs a fix.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: