Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
adamjs
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
adamjs
4mo ago
This seems more like a chromatic aberration "hack" for HDR landscapes (intensely-lit portions of the scene would have color fringing apparent at the boundaries of light/dark due to dispersion in the observer's lens). (An
2.
▲
by
adamjs
9mo ago
They might want to check out what VNC has been doing since 1998– keep the client-pull model, break the framebuffer up into tiles and, when client requests an update, perform a diff against last frame sent, composite the updated tiles client
3.
▲
by
adamjs
2y ago
Two use-cases jump to mind: * Allows incremental porting of large codebases to ARM. (It's not always feasible to port everything at once-- I have a few projects with lots of hand-optimized SSE code, for example.) * Allows usage of thir
4.
▲
by
adamjs
3y ago
We wrote exactly that for our game-focused port of WebKit [1]. CPU renderer uses a tiny, custom fork of Skia (we only use the path rasterizer and their SSE2, AVX2, NEON backends) and our GPU renderer draws directly on GPU via tessellated pa
5.
▲
by
adamjs
3y ago
Every language has its own merits, there's no single language that's universally the best for every task. With that said, C++ and Rust both occupy similar domains (high-performance, low-level, often interacts with OS syscalls or h
6.
▲
by
adamjs
4y ago
hey Nate! I still remember-- new website looks amazing! For sure, feel free to hit me up on Discord if you want to chat.
7.
▲
by
adamjs
4y ago
Ultralight is definitely not abandoned, 1.3-beta will be released end of this week (nightly builds have been available for the past year) and ARM64 support will be available in the 1.4-dev branch later this year. Feel free to contact me at
8.
▲
by
adamjs
4y ago
Definitely not a fork of WPE (which is primarily tied to *nix), Ultralight is built on a platform-agnostic fork of WebCore/JavaScriptCore I started back in 2015. The goal is actually more ambitious than WPE since we run on every platfo
9.
▲
by
adamjs
4y ago
Hah I could write a whole post on this topic but ultimately after experimenting with many different approaches on real-world hardware, tesselating the paths and using multi-sampling for AA (you can limit the MSAA to a single area via offscr
10.
▲
by
adamjs
4y ago
WebKit is BSD but has sub-modules with LGPL code (specifically WebCore, JavaScriptCore, and WTF). Ultralight is not WebKit (we have a totally different API and use our own renderer, compositor, and event-management code) but we do use a for
11.
▲
by
adamjs
4y ago
Yes-- Ultralight (the renderer underneath) has two modes: pure-CPU or pure-GPU. The GPU renderer does all drawing on the GPU using tesselated path geometry and pixel shaders. All painting is actually emitted as virtual GPU draw calls, inter
12.
▲
by
adamjs
4y ago
Ultralight dev here-- I've been on the dev-tool side of this equation for the past 13 years so I have insight into why people are actually using HTML/JS/CSS over proprietary UI tech on the desktop. It's several things--
13.
▲
by
adamjs
4y ago
Yes-- WebCore has an internal Accessibility API that I'm going to expose in 1.4 to be either handled by the embedder (so you can determine the best way to display / navigate that information) or handled by AppCore (we provide stoc
14.
▲
by
adamjs
4y ago
Ultralight dev here-- I remember the KDE days too and have released a fair amount of my software free and open-source. I had indeed contemplated making Ultralight fully LGPL and charging for support but decided that the incentives really di
15.
▲
by
adamjs
4y ago
Ultralight dev here-- most work has gone into porting Ultralight to various platforms (game consoles and ARM64) the past 2 years. The main focus is less to replace Electron and more to get modern HTML/JS/CSS running everywhere. Th
16.
▲
by
adamjs
6y ago
Yes, Texan here, our neighbors had their faucets dripping but lost power/heat for 30+ hours and pipes froze and burst in the ceiling. Several factors involved—- the pumping stations lost power so water pressure fell to a trickle. Also
17.
▲
by
adamjs
6y ago
It's definitely still a concern! And our community is growing (come check out our Discord [1]). Our advantages are much more than memory usage-- it's also distributable size, low-level integration, single-process mode (no external
18.
▲
by
adamjs
6y ago
Gave more clarification on this in a reply to parent comment.
19.
▲
by
adamjs
6y ago
Hi there, author of UL and Awesomium here. We didn't abandon anything, we announced to the community that we were stopping development of Awesomium (our previous Chromium fork), are going to build something new (which turned out to be
20.
▲
by
adamjs
6y ago
Yep, we maintain an Xbox port and are porting to PS4, PS5, and Switch next. Yes, the GPU renderer (and CPU renderer) took about 4 years of R&D alone to get to a usable state (we started on GPU rasterization long before WebRender was eve
21.
▲
by
adamjs
6y ago
Yep, We hit a wall when developing Awesomium-- long story short, the vision for Chromium long-term didn't match with our design goals so we announced to the community that we're starting over with something new (which turned out t
22.
▲
by
adamjs
6y ago
Somebody just posted our top-level packager GitHub repo to HN instead of our website. (And hey thanks! I wrote that by hand a few months ago :))
23.
▲
by
adamjs
6y ago
Yep, Xbox port is nearly finished, PS4, PS5 and Switch ports are next.
24.
▲
by
adamjs
6y ago
I can enable accessiblity features and API to make the library more amenable to screen readers and other modes of browsing. So far the library has primarily been used in games (which have less accessibility concerns) so we've been focu
25.
▲
by
adamjs
6y ago
FWIW Ultralight isn't tied to GTK or any windowing system (API is platform-agnostic), also the core Renderer API doesn't even require a run loop (this is vitally important if you're integrating HTML UI into complex environmen
26.
▲
by
adamjs
6y ago
90% of our code is open-source under LGPL and available on GitHub [1], [2]. The distribution as a whole (and core renderer) is under a proprietary, non-free license with provisions for usage in free software. Also the license does not forbi
27.
▲
by
adamjs
6y ago
Yep, this is correct! I'll update website pricing to make this more clear.
28.
▲
by
adamjs
6y ago
Thank you!
29.
▲
by
adamjs
6y ago
Lead dev of UL here, we didn't post the link, and our GitHub repo is def not clickbait (the top-level repo is just the packager and samples), 90% of our code is open-source under LGPL and available on GitHub [1], [2]. The product as a
30.
▲
by
adamjs
6y ago
Hi there, lead dev of UL here (we didn't post the link, HN just found our beta :)). That top-level repo is just our packager/samples, 90% of our code is open-source and available on GitHub (released under LGPL), see our WebCore [1
More ›