Top all-time · #15181
TeamDev
Company blog · teamdev.com/mobrowser/blogprogrammingweb
TeamDev is the company blog at teamdev.com, writing about programming and web. Since 2016, 5 different Hacker News readers have linked it 10 times. It is still writing: the last post was on 2026-10-08, and you can follow it by feed.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
HN commenters mention TeamDev mainly as the maker of JxBrowser and DotNetBrowser, Chromium-embedding libraries for Java and .NET. The comments do not judge the blog's writing.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
TeamDev is a software development company headquartered in Lisbon, Portugal. The company's product portfolio includes web and enterprise development solutions and Java-native integration libraries. Along with products for developers TeamDev has been providing cutting-edge development services to cus
Most-linked posts?
- /jxbrowser2 people · 3 mentions · first linked 2019-04-25
What Hacker News says?
To add to this, if you like concept/portability/cost-effectiveness of Electron but don't want to mess with the Node/npm ecosystem, there are chromium embedded frameworks out there for Java and Python[0][1][2]. [0]: https://bitbucket.org/chromiumembedded/java-cef [1]: https://github.com/cztomczak/cefpython [2]: https://www.teamdev.com/jxbrowser
Comment linking /jxbrowser
on “Flutter desktop shells”Submitted Show HN: DotNetBrowser – Embed Chromium into .NET Applications as a story · 7 points
HN discussionI am actually currently working on something similar but instead we opted to use JxBrowser[1]. It's basically what Electron used to be but has Chromium embedded into the JVM instead of Node. [1]: https://www.teamdev.com/jxbrowser
Comment linking /jxbrowser
on “Clojure on the Desktop”Submitted Show HN: MōBrowser, a TypeScript-first desktop app framework with typed IPC as a story · 2 points
HN discussionI think JavaFX could have been more successful if they would have managed it differently. I really liked it. The JavaFX developers were all great to deal with and would help you as much as they could. One of the problems in my opinion is that once you went up the chain beyond the developers, it seemed like there were some people that didn't understand what they were doing or didn't care or possibly both. They had ta…
Comment linking /jxbrowser
on “The decline and fall of Java on the desktop”Submitted What's wrong with Electron IPC and how it could be improved as a story · 2 points
HN discussionTeamDev, quite popular amongst large businesses with Chromium-based widgets for Java and .NET. JxBrowser: https://teamdev.com/jxbrowser/ DotNetBrowser: https://teamdev.com/dotnetbrowser/
Comment linking /dotnetbrowser/
on “Fake job seekers are flooding US companies that are hiring for remote positions”Submitted Source code protection in JavaScript desktop apps as a story · 1 points
HN discussionI've been working with Electron for a while, and one thing that keeps bothering me is how IPC is designed. I mean, it's pretty good if you write a simple "Hello, world!" app, but when you write something more complex with hundreds of IPC calls, it becomes... a real pain. The problems I bumped into: 1. No single source of truth for the API between renderer and main. 2. Channel names are just strings (easy to break, h…
Comment linking /mobrowser/blog/what-is-wrong-with-electron-ipc-and-how-to-fix-it/
on “What's wrong with Electron IPC and how it could be improved”