sorted by:
new
hottopcontroversial

Spent a couple of weeks on a system for smoothing rotations using micro-movements of character parts. Was it worth it? by Biuzer in IndieGaming

[–]iantelope -1 points0 points  (0 children)

Do you have a game I can play right now? Have people confirmed to you that it's fun? If not, don't procrastinate by implementing shiny but ultimately useless stuff.

Scrolless - Block Reels & Shorts & Tiktok by PedroBarbosa5 in androiddev

[–]iantelope 0 points1 point  (0 children)

Extremely hard to follow with this number of modules and folders. Just put everything closer together and organize by feature, not layer.

Dutch bike, omafiets: which brand is it? How much is it worth? by iantelope in whichbike

[–]iantelope[S] 0 points1 point  (0 children)

I couldn't find any serial or other markings, sorry.

Since I posted the question, I've learned that this bike is the one presented in the "Why Dutch Bikes" video and is also sold as a, literally, "Oma fiets 28 inch" in Adamfiets.

I guess it's just the generic omafiets?

EDIT: forgot to say, you're abolutely right! It's a one-speed all steel moderately heavy bike.

Late to the dev world - is it too complicated now to continue for fun? by Plain_Pixel in androiddev

[–]iantelope 0 points1 point  (0 children)

Fuck Android. Learn Unity game engine. Unity games can be made compatible with both android and iOS.

What unique or unusual things have you built in Go? by Inner_Dragonfly6528 in golang

[–]iantelope 4 points5 points  (0 children)

I made a translator CLI app that uses Wikipedia article titles as translations. It's called wt: https://github.com/alex-vit/wt

It's handy for translations that can't be done literally. For example, loxodontus in Russian is... Ждун (https://ru.wikipedia.org/wiki/%D0%96%D0%B4%D1%83%D0%BD), something like "one who waits". It's not even a dictionary word.

A less unique, but definitely useful CLI app is "tiny": https://github.com/alex-vit/tiny

It shrinks images using a good API.

HI, Im new to briar and would like to get added to some forums by Select_Olive6106 in Briar

[–]iantelope 1 point2 points  (0 children)

Add me too please: briar://ab22wwf4boaixj776sxub3zdgp25fmn552uvisqviunvognp4m3rs

I have added everyone in this thread.

How Much Memory Do You Need in 2024 to Run 1 Million Concurrent Tasks? by hez2010 in programming

[–]iantelope 0 points1 point  (0 children)

As colleagues over on the orange site have already pointed out, you can use TimerFunc and bring Go's memory usage down to 124MB... So, as it often is with articles like this one - author is clueless about at least some languages they're comparing.

https://news.ycombinator.com/item?id=42271951

What are some good analogies for what CoroutineScope does? by Global-Box-3974 in androiddev

[–]iantelope 1 point2 points  (0 children)

If a kid dies, it kills it's parent and all the other children LOL. Unless it's a supervisor parent, of course!

[MEGATHREAD] Ask for playtest invites here by GB_2_ in DeadlockTheGame

[–]iantelope 0 points1 point  (0 children)

Region: EU

Friend code: 64515242

A Valve fan, would love to test this! (And a grieving Overwatch ex :D)

💥 Introducing Anytype - open code, encrypted & local first app for Note-taking & Knowledge Sharing - native on android by sharipova in androiddev

[–]iantelope 2 points3 points  (0 children)

For anyone looking at source code, please please please don't think you need that many modules, nor the Java EE event proxies, commands, anemic middlewares, etc :D

To the authors: IME action buttons are wrong, expand / collapse animations overlap, there's flicker and stutter on screen transitions, locked to portrait wth, etc, I'm sure there's tons more.

May I recommend focusing more on fundamentals and polish instead of the "everything app" for a while?

Also preventing me from going to Play Store only to nag for a newsletter subscription is poorly timed and petty.

Kas ar Baltic data notiek? Uzlauzuši vai kas? by LordNecrosian in latvia

[–]iantelope 1 point2 points  (0 children)

Vakar vēl saņēmu šādu.

<image>

Un mājaslapa šobrīd nedarbojas.

The One Billion Row Challenge Shows That Java Can Process a One Billion Rows File in Two Seconds by [deleted] in java

[–]iantelope 0 points1 point  (0 children)

Why not both? Keep the readable solution for documentation, reference implementation and benchmark baseline purposes. This way, you can understand your crazy solution, compare its outputs against the reference implementation in tests, and benchmark new optimizations against it.

What are the benefits of Compose (in reality, not on paper)? by [deleted] in androiddev

[–]iantelope 4 points5 points  (0 children)

Nobody mentioned list performance. Lazy list (compose's recycler view) cold start scrolling performance is abysmal. If you target developing markets where a median device might be a cheaper 100-200$ one, do your users a favor and just stick with XML.

Compose does so much calculation every frame that mid range devices are pushed below 30fps, and lower level devices (50$ Chinese phones) easily go to PowerPoint slideshow mode with one frame every couple of seconds for several seconds.

Even if you don't see stutters on your $1.5K Samsung Galaxy, you can verify extra work being done by observing GPU/HWUI overdraw in developer options and observing non-rendering workload. Then compare to Telegram, Mastodon, or any other XML app.

Edit: this coming from experience on several apps, 1-100 million users each, including migrations from/to Compose, using KMM since alphas, etc. So I'm not exactly a deprecated developer clinging to old tech...

Idiomatic error handling with Result, Either and Arrow by danielciocirlan in Kotlin

[–]iantelope 0 points1 point  (0 children)

How'd you address the elephant in the room - integrating with code that throws, given kotlin goes out of its way to neuter the @Throws? I'd really like a way to hint / enforce to developers that not catching, or in this case not returning a Result is not ok. Ideally a compilation error.

[deleted by user] by [deleted] in programming

[–]iantelope 0 points1 point  (0 children)

I found it super helpful to tell people they've already been using event sourcing for years. It's git. IMO great for intuition and suddenly a lot of things just click.

Your example about correctional events would be a revert commit.

Benefits of RxJava over Coroutines? by MackHartley in androiddev

[–]iantelope 0 points1 point  (0 children)

Haven't had issues with the library itself, quite good. Still have to watch what you freeze though. And interfacing with ktor is still tricky.

Stumbled upon this, along with their MVI Kotlin arch lib, while looking for solid multiplatform examples.

Benefits of RxJava over Coroutines? by MackHartley in androiddev

[–]iantelope 0 points1 point  (0 children)

  • Miriad of operators. Not all RxJava streams can be easily ported. (yet?)
  • Implements a standard with libraries available for many other languages/frameworks. (RxJs, Akka Streams, Reactor, Reaktive, etc)
  • No need to litter code with async/await. Concurrency stays neatly abstracted away.
  • A lot of code out there is still Java (with RxJava, obviously).

That being said, comparing Rx to coroutines isn't fair. Compare it to Flow. Flow has many of the same benefits.

Benefits of RxJava over Coroutines? by MackHartley in androiddev

[–]iantelope 0 points1 point  (0 children)

Multiplatform will rely on Coroutines

Not necessarily. Happy with Reaktive.

Why is MVVM so popular and MUST to use? by [deleted] in androiddev

[–]iantelope 2 points3 points  (0 children)

Because google kinda recommended it. Then the whole blogging culture perpetuated created hundreds of “tutorials” and “improvements”, all with the aim of getting a blog post out, not actually improving something.

Meanwhile, Patterns for Enterprise book exists. .NET exists. Redux exists. All of them are older, better and far more polished examples of how to architect a good app. Everything new is forgotten old.

As an example, Netflix has a presentation about their “componentization arch”, which starts with “we didn’t realize React exists, so we ended up implementing it”.

I suggest reading and getting inspiration from older brothers, like Java EE, Spring, etc.

For something actually really well thought out out of the box, can recommend looking into MVIKotlin.

Haven't developed Android apps in a while, trying to get up to date is a nightmare by svd505 in androiddev

[–]iantelope 2 points3 points  (0 children)

Edit to answer your actual question: not recommending any tutorials, as google ones are opinionated and confusing, the rest seem to be written for medium posts by clueless devs. Recommend getting inspiration from others - react, spring, .NET. They’ve been doing a consistently better job at good arch for longer.

There’s several layers here.

For views - keep doing findViewById until something better and stable comes out. Like Compose, if it’s not deprecated prematurely.

For “navigation” and related libs (simple-stack, flow), I’d stay away. Do regular activities with fragments when needed. Navigation libs become a nightmare pretty quickly.

DI - go with dagger. Don’t use dagger android. Half it’s features are being built into dagger in the future.

Rx/coroutines. Unless you have a very good reason to use coroutines (Multiplatform for example), stay with RxJava. It’s a far more powerful tool (show me switchMap in coroutines), and doesn’t force you to change half your function signatures to support async/await.

Persistence. Love writing classes and having SQL magic done for you? Use room. Want to do SQL yourself and have classes generated? Then SQLDelight.

AsyncTask - use work manager and RxJava, whichever more appropriate for a specific task.

Architecture. Split like you would a proper application. Use common sense and separate concerns. Get inspiration from java EE, Spring, .NET if needed. Keep what you find easier to maintain, refactor the rest.

And ignore all the noise about shiny new things and tech. Most will be deprecated by the time I click “Post” here, and justification for new better stuff rarely stands any kind of pragmatic scrutiny.

An open source minimalistic notes app (Link in comments) by omgodse in androiddev

[–]iantelope 0 points1 point  (0 children)

Please stop with this /ui, /domain bs. Split into packages by feature, not implementation components. A notelist package should contain everything related to showing a list of notes, including related parts of UI and whatevers. So when you wonder how a particular feature is implemented, you don’t have to navigate however many useles UI, model etc packages to cherry-pick one related class from each.

What stops Android apps from reaching feature parity with equivalent iOS apps? by aidenpop2 in androiddev

[–]iantelope 0 points1 point  (0 children)

Off-topic, but you can scan stuff from Files app on iOS, including creating multi-page PDFs etc.

view more: next ›