• Content count

  • Joined

  • Last visited

1 Follower

About b10b

  • Rank
    Advanced Member

Contact Methods

  • Twitter

Profile Information

Recent Profile Visitors

2,060 profile views
  1. A game I made for a client

    I liked the shuffle and bonus buttons ... a smart feature / workaround for grid tile arrangements with an odd one out! Gameplay felt both slick and solid - good job.
  2. It is miraculous to share a creative experience with anyone, anywhere - without language barrier, cost, or perceived complexity. Browser games are an example of such simplicity.
  3. Web UDP - public demand

    Netcode.io is a solution that uses what currently exists to design around the problem - it's great to see such an implementation approaching a mature state. But the issues remain: use case is marginal, support is spotty. Will that change? I am sceptical there exists a significant untapped audience of gamers who seek UDP experiences in their web browser. Instead I see gamers who are conditioned to install for optimal experience (apps) or accept latency for convenience (web). If there exists more benefits for a wider group of users then perhaps gathering data and adding that to the proposal would be beneficial?
  4. Deploying games to Android.

    The retirement of Intel XDK is a real shame - it worked and had big obvious buttons. I'd used it for many commercial projects (all still live) and considered that Intel would be in it for the long haul. It's closure is a reminder that any cloud based services can be here today, gone tomorrow. Stay backed-up, flexible, portable, non-proprietary!
  5. Be cautious of auto-conversion and magical reuse of existing AS2 content. Google's Swiffy was really good for automated AVM1 conversions - but still a long way off from providing a decent modern (i.e. mobile) web experience to the user - hence it was deprecated. By the sounds of things OP requirements don't revolve around high framerates or other game-oriented features - so should avoid limiting options to game engines. Text-priority e-learning may find a better fit with React (or similar SPA approach).
  6. Hurray for BC! Emailed directly.
  7. iOS Emulator

    @TheBoneJarmer BrowserStack (or similar) might do what you need for such a test?
  8. iOS Emulator

    Likely best to ignore the adware / spamware claims - if a decent full-featured iOS emulator worked well it'd probably be bundled into iTunes? That said, emulating / virtualizing specific aspects of the iOS workflow and user-experience is possible from Windows. What are you developing and what do you wish to test?
  9. Sell local. Record the game to a C15 (or CD if you want to take half the fun out of it) and list it in a classified ad in the local paper. Let me know how it works out for you!
  10. convert a .svg in a .json

    Try the Cheerio lib within your node app - I've used it extensively for server-side SVG manipulation and found it to be a reliable and stable library. https://cheerio.js.org/
  11. Scared of Typescript

    Build commands ... I suggest using Webpack with TS and have it running in "watch" mode, so as a file is saved it'll auto recompile. That way the TS compiler aspect is effectively hidden from the hands-on workflow. Result is: 1) write code, 2) save it, 3) view the HTML5/JS in browser, 4) repeat.
  12. Use arrow functions?
  13. Good job on the beta and I enjoyed your 16-bit nostalgia, hidden features and retro aesthetic. Some feedback you may wish to consider: 1) controls didn't work on mobile (when I tested last week), 2) the tight scrolling view is unhelpful when playing a Pac clone, 3) trademarks. Good luck!
  14. Which Typescript IDE

    Yes, I'm a daily TS user and would say since TS2 that VS Code has become my go-to IDE (small, mostly quick, does the job out-of-the-box and is linked to the release cycle of TS). I used Atom prior and it had some nice workarounds for the limitations of TS1 tsconfig, but I found it increasingly unresponsive dependent upon the size of project, and the workarounds were no longer of benefit (to me). Both of these IDEs use a webview, which may be the cause of the graphical performance issues I encountered - notching them into fullscreen modes can improve things.
  15. JavaScript Framework's

    I understand the appeal of a hidden army, and I agree for trivial issues or initial learning curve this is valuable beyond words. However I've repeatedly encountered long-term frustration with any external dependency (no matter how large or stable today) because we're betting our future on other people's agendas - and the two will diverge over time. Whereas self reliance and the ability to fix / invent / adapt is the key to being original (more of a cultural thing than a purely technical thing) plus it provides resilience through diversification opportunities. Perhaps picking a framework that can easily make what exists today paints us into a corner to make more of the same? Or perhaps it's obviously the best choice for today?