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

def package this and put it on the App Store before clones eat your lunch. Would happily pay a couple bucks to play this on my phone offline.


Thanks. I packaged on the play store (free). Nobody seemed to care, and it got 0 downloads. It's now on f-droid too, where I got a nice message from a random user. Maybe I should make a paid version for play store/app store/steam, while continuing to give the same game away for free on web and f-droid (it's OSS). I don't like really like app stores and their annoying rules and monopolies, though. And I feel like they don't promote good stuff, they only push adware in front of visitor because they get a cut of the ads, so even if I package the app and publish it (ad free), the stores will probably push the clones. I might eventually make the move, but for now I'm happy to make good OSS software.


I was a Kagi subscriber for about 5 months. I had noticed a slight improvement for random software development related content vs my previous search engine (bing). After cancelling 6 months ago I don't miss Kagi at all.

The thing that made me cancel my subscription was one specific interaction.

One day I was trying to buy tickets to a podcast tour, the sales for tickets was set to open at a specific time and I was searching for the purchase page at the moment of opening. I frantically searched "$SHOW_NAME $CITY tickets", the first search failed to bring relevant results. I tried "$SHOW_NAME $CITY tickets $YEAR", nothing.

I tried many searches for about a minute along these lines and thought maybe their site just wasn't public and I needed a specific link. Then I typed my original "$SHOW_NAME $CITY tickets" query into bing and got the exact correct webpage on the first try.

Bought the tickets I wanted and immediately cancelled my subscription to Kagi.


There was a talk given on this subject at iOSoho if ya want to take a peek:

https://youtu.be/8ApcIOZe9qg?t=1921


following the dynamic part of this, it looks like they recommend DotJS.

https://sitejs.org/#dynamic-sites

I am not too familiar with DotJS, but it looks like its depreciated/unmaintained for years.

https://github.com/defunkt/dotjs


https://github.com/olado/doT is what they are talking about I think.


That dotjs is for user scripts (ie a chrome extension) not for the thing their talking about which is php for node.


Some devs prefer a GUI even when a perfectly good command line tool exists. For example the many git wrappers.


FYI you have a ref to 0.0.0.0:8000 as your homepage from the docs.dcpm.dev link

<a href="http://0.0.0.0:8000/" title="Docker Compose Package Manager" aria-label="Docker Compose Package Manager" class="md-header-nav__button md-logo">

edit: looks like a cool project though! congrats on shipping!


thanks, I'll push a fix


>Assembly Makes Flask Great Again

The fact that flask can bar a basis for other frameworks makes Flask (and werkzeug) great in itself.


This phrasing turned me off. In the USA there are political connotations such that to over half the population, the meaning of 'making great again' is the exact opposite.


I didn’t realize Flask wasn’t great?


In their defense, some other languages make the length of a string an attribute/property on a string instance. Python feels like the odd one out here making it a free function you must pass an instance to.

If the tech lead spent a lot of time working with another language that made the length an attribute, I think it would be reasonable for them to need to look it up often.

https://apidock.com/ruby/String/count https://docs.oracle.com/javase/7/docs/api/java/lang/String.h... https://developer.apple.com/documentation/swift/string/30035...


Rx has a bit of a "namespace collision" with the functional reactive programming library ReactiveX, which has implementations in many different languages. Often these libraries are called Rx(Java|Swift|Ruby|PHP|js|$LANG).

Paradigm: http://reactivex.io/ Implementations: http://reactivex.io/languages.html

That being said the editor looks very cool! Congrats on shipping!


Apparently there is already one for Rust too. https://github.com/ReactiveX/RxRust


You say "already", but the repo you link to hasn't been updated in nearly five years


Yes. That's how time and tense works.


And an even bigger "namespace collision" with it being the common shorthand for medical prescriptions


Another Namespace collision with iZotope RX (a audio retouche tool).


The editor does look cool. Maybe it should be called rxl rhymes with pixel.


people bring this kind of thing up in every thread as if it's a useful comment for either the reader or the poster (presumably project author). it's almost as common as "this page sucks on mobile".

who cares? we all know how to use Google by now to narrow results by adding qualifying keywords to the query; it's not like I'm just going to search "rx" or even "rx rust" when I'm looking for this project (probably "rx rust pixel"). it's a complete non-issue.


I care. Also it's a potential legal issue for any given project if there's a registered trademark involved.

Plus first result for "rx rust" lead me to https://github.com/ReactiveX/RxRust


> Also it's a potential legal issue for any given project if there's a registered trademark involved.

At some point we will have to generate random strings for the name of our projects because all the "good" (or even "bad") ones are taken. :P


Already a thing: https://namelix.com/app/?keywords=poop+scoop

Highlights for a "poop+scoop" related startup include: Flingo, Trash.ly, Fastpoop, Stinkere, Guunk, and Spoop


I'm surprised it didn't come up with Scoopr.



Let's keep in mind that this is an end user application for pixel artwork. You and I might care that it's Rust. End Users will not. It could be written in Malbolge or BF for all an end user cares about.

Namespace collision is gonna be a pain for end users and newcomers, possibly depressing discovery, which is our point.


Why would you image an author would not care that their page "suck on mobile". If they are posting/sharing their stuff, they more than likely want people to consume (and spread/reshare it). Both being poor experience on mobile and non-discoverably, hard to search for impact that.


i'm sure the author cares. what i'm not sure about is that the author isn't aware and that "hey your site fails on mobile" is of much use to them.


I can easily imagine an author who rarely uses their own mobile page except to make sure that it works at all; or who knows it's not great, but doesn't realize just how annoying it is; or even who has never looked at their site on mobile, ever.


Does anyone have this info in a nice info graphic? I would love to hang this in my kitchen as a quick reference.


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

Search: