HackerTrans
TopNewTrendsCommentsPastAskShowJobs

nsfmc

1,058 karmajoined 17 yıl önce
http://nsfmc.tumblr.com and also http://generic.cx

[ my public key: https://keybase.io/nsfmc; my proof: https://keybase.io/nsfmc/sigs/e9YAe_1k0aJVxOOadbxGJm6s_cFKeMeuWay_ocZyl50 ]

Verifying my Blockstack ID is secured with the address 12yroXUpFaXP4bL9wxw3LARRX8Be8HYZui https://explorer.blockstack.org/address/12yroXUpFaXP4bL9wxw3LARRX8Be8HYZui

comments

nsfmc
·13 saat önce·discuss
you listen to the audio and try to determine if you can either read or understand the audio. it's repeated twice, once formally and once casually, so good for listening practice, but also good for adding new words/phrases into your vocabulary since some of them might be familiar but maybe reconfigured in a way that you don't normally see in your practice.

this is probably only useful if you've started learning a very small amount of grammar, know hiragana well enough to make furigana useful, and have started memorizing enough kanji/vocab to make 'overheard train chatter' useful. probably, generously, something maybe 3-6 months into your japanese language journey, so not good for bootstrapping.
nsfmc
·4 ay önce·discuss
> For every HTML 2.0 you might have tried, you were just as likely to have got stuck in the dead-end of Flash.

i'll just say, and i understand this is not the point of the article at all, but for all its faults, if you got in on flash as earl as html 2.0 and you were staring at an upcoming dead-end of flash in say, 2009, you also knew or had been exposed at that time to plenty of javascript, e4x and what were essentially entirely clientside SPAs, providing you a sort of bizarro view of the future of react in a couple of years. honestly, not a bad offramp even if flash itself didn't make it.
nsfmc
·geçen yıl·discuss
unless... maybe... https://www.ox.ac.uk/news/2017-03-28-tetris-used-prevent-pos...
nsfmc
·7 yıl önce·discuss
great, now you have a native client but now your customers will expect that it works offline, so now you're building a sync system for your app.

additionally, if your app has any design/layout issues, now you need to hire for people that can do visual layout using tcl/tk.

If your app consumes rich text, you're in for a real treat as you are now on the hook for figuring out how to manage that as well (in addition to serialization, you also need it to likely be emitted into some web friendly format anyway. if your app consumes some feed (say new-user facing features or whatever), you need to find some meta-format that your app can use to layout that content (or i mean, i guess you can use a webview, but then...)

if your customers are enterprise-ey, you are now dealing with some overzealous IT dept that is skeptical of your application running with user permissions.

if you're trying to push a fix/update to your users, you now need to build infra around deploying new apps as well as customer support determining if users are somehow running old versions when they report a bug.

the web is a total "mo money, mo problems" situation, but i think people dismiss how many problems the web solves for your developers on a day to day basis: easy to push updates, simple to whitelist your app's domain on some restricted network, easy add dynamic content/layout to portions of your app with stored content, (less sync resolution issues because your app probably requires network to operate) etc. Native apps have their own issues, they're great, don't get me wrong, but people demand a lot from basic apps of any stripe these days, and as those requirements increase, so does the amount of complexity that developers need to manage at all stages of the pipeline.