Hacker Newsnew | past | comments | ask | show | jobs | submit | lucasmerlin's commentslogin

I use it in https://malmal.io for rendering the drawn tiles on my server, it works really well.


I'm using egui to build an app with a mobile ui and I'm really enjoying it so far. The main reason I chose egui is because I need tight integration with wgpu and this is really seamless with egui.

In the process of building my app I have also created a couple of crates for egui that add drag and drop sorting, infinite scroll and other utilities.

In the example showcasing my crates I also try to show that you can make a pretty ui with complex layouts using egui (check the gallery and chat example): https://lucasmerlin.github.io/hello_egui/

I've had to spend a lot of time improving egui and it's ecosystem in the process of building my app but it seems to be worth it.

If you're not building a graphical app it probably makes more sense to use something like tauri or flutter as the gui to build a cross platform app with rust, at least until it's gui ecosystem matures.


It can be a huge difference. Say this month I only listen to a completely unknown artist. I am the only person listening (to make the calculation easy). I've listened to 10 of his songs and this is everything I've heard this month.

Now if my 7$ are distributed to all artists I've listened to this artist will now receive 7$. If my 7$ is thrown in a global pool and split by global stream counts this artist gets almost nothing.

Of course this is a extreme example but it should illustrate why this can matter.


> If my 7$ is thrown in a global pool and split by global stream counts this artist gets almost nothing.

Not by definition. If you generate more streams this month than the average user, your streams are a larger fraction of the stream counts than your 7$ is of the revenue pool, and this artist will get paid more than if he only got your 7$.

Splitting the revenue per-user instead of per-stream can certainly make a huge difference, but switching to per-user instead of per-stream benefits artists with listeners that generate a below-average amount of streams per month, regardless of their absolute stream numbers.


We've been having a lot of problems with weird bugs with nextjs, so I can't really recommend it. Feels like it's a eternal beta.

First, we've had a problem with nextjs not caching the response code for 404 pages, so 404 pages would have a 200 status code. Now they've fixed this they have a bug where they are caching the 304 response code, responding with 304 to every request and completely breaking the site. This has been open for a month now and has affected a lot of people but it seems like Vercel just doesn't care.

https://github.com/vercel/next.js/issues/56018


Yep their github management is atrocious. I understand it's a popular product so you get a lot of low quality issues opened, but there tons of real problems where no developer ever appears, and then are closed by the bot because of inactivity.

Infuriating. The longer I do this, the more that issue management responsiveness becomes a real consideration when choosing a dependency.


I’m not trying to victim blame but why not fork and fix the bug? Isn’t that the point of open source? If you’re not paying for support then I feel you should set expectations accordingly. Do they offer any kind of sla or some other guarantee on responding to an issue?

(I work in enterprise stacks where there’s a hard contract that defines these things so maybe biased)


Yep absolutely, I agree and understand how much we're getting for free.

On the other hand, their marketing and hype machine has gotten the industry at large to buy into their product. So when you promise enough to get companies to move to your (free, open source) tech stack, but then are MIA when there are issues... I am of two minds.

But yes at the end of the day you're right.


This is my big problem with proprietary software; and why open source pragmatically makes more sense.

Fixing bugs is down to priority and incentives of the parent company.


I mean it is open source and someone even made a PR to fix the bug in question and I guess I could use their fork until it's fixed.


I was about to say, just fox the bug submit a pull request and use your fork until it’s merged. Isn’t that the point of all these fancy source control tools?


Hmm, doesn't seem as much of an issue now.


I made collaborative painting apps, https://hellopaint.io and https://malmal.io (there might be some slight NSFW content). In the best months I made 800€+ in ad revenue from malmal but currently it's a lot less. I think there's potential to make a lot more though, although I'd like to stop showing ads and switch to some more predictable income model. I do have a patreon but it only brings in ~100€ per month. I could promote it more though.


Awesome work! Saw some furry porn being drawn live on the front page, that was kind of funny :"D


That was really fun!


Maybe via bluetooth? I'd imagine that would be the easiest way.


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

Search: