HN user

snodnipper

53 karma
Posts0
Comments34
View on HN
No posts found.

Personally, I have been very pleased with the results despite the limitations.

Like many (I suspect), I have had several users provide comments that the AI processes I have defined have made meaningful impacts on their daily lives - often saving them double digit hours of effort per week. Progress.

clearly could be a problem...but you are really looking at feature extraction / terrain analysis and best guessing with what is available (little different to a human doing the same job). The main thing here is that storage is so cheap and light that these these systems become easily possible. Terrain, features + building heights...filter if you need on building height / terrain...work with what is left...

I agree - I have used the gimp since 1998 and when using other apps (e.g. Affinity) I often return to Gimp and Inkscape because I understand their UIs best.

I was a massive GWT fan - particularly because it played well with the Java ecosystem.

1. huge programmer pool 2. tried and tested legacy code could be easily used / adapted 3. code quality / checkstyle plugins just worked 4. great testing tools

My main gripe was the compile time (often 2-3 mins)...whereas Adobe Flex would crank code out in 3 seconds.

Now, the new language models should help us push through the noise.

agreed...at what point should I provide remuneration to my professors? Should those professors / staff provide royalties upstream? I fully agreed with citation _but_ to claim that AI is derived work / needs to return royalties based on the materials it learnt from seems a step too far IMHO. It read material and put it back like everyone else.

Bob was an incredible guy - we've lost wonderful tech leader _but_ I am so terribly sorry that his family have to go through this

I can never actually pay for anything on Uber eats - nothing unusual...Australian banks all the way and yet still impossible to order.

Menulog and DoorDash appear to work pretty well. Sad to see Deliveroo go.

My biggest source of burnout of late is the MS Power Platform. Being under pressure to deliver with half baked tools due to "political demands" made the vast majority of us consider other options.

Today, we learned that we will no longer be using much of the "Power" Platform...but we have all wasted a year of our lives "trying".

Now that we are done, I look forward to getting back into the gym before using "traditional" tooling that actually works.

In the future I will be more careful with the projects I work on - with a preference for mature technologies. Erlang, Java, RDMS, Rust etc. sure. Latest shiny from tech company where people hate their jobs - NO WAY. They will bring us all down.

Flutter for Linux 6 years ago

Flash remains the most productive UI development environment I have had over the past twenty years. Getting graphical apps working on all major platforms is a fabulous achievement by the Flutter folks.

I have no love for what Android has become and where Kotlin is going. The web today feels like a PDF...huge amounts of movement but not necessarily progress.

I hope more than anything that Flutter continues to gain traction. To my mind it is perfectly reasonable for next generation tech to write to the canvas with the latest widgets as long as there is good accessibility support.

Adobe Flex was my most productive client development experience over the past 20 years. I transitioned to Android _but_ there were many hideous things with that (e.g. ghastly emulator, legacy Java support etc.).

My personal hope is that Flutter gains traction and the web can move beyond current web/native technology. Postscript / PDFs aren't suitable for game experiences...and to my mind web standards have been shoehorned into supporting web apps, where there is a mismatch with native technologies. I'd like to think that Flutter can help bridge that gap.

This is not to say that accessibility etc. should be ignored...nor better support in Firefox...but even Brendan Eich is using Blink/V8 with Brave.

Anyhow, thoughts of one.

I have been developing Android apps since the beginning, although I have cut back my time on Android largely because it is a filthy experience. How many times have we mashed the feedback button and still end up with a terrible emulator? A non-issue for iOS folks.

Flutter represents a great opportunity imho to uplift development capability and avoid needless fragmentation. It reminds me of Adobe's Flex in some ways and I can assure you that I have _never_ had such a productive client-side development environment since! Flex united developers, graphic designers, animators etc. 3 second build times...worked on everything even if the runtime was cough 'sketchy'. I'd love to see Chet Haase move onto Flutter and resume similar videos to his Adobe days.

As for all of the Kotlin noise, like much of Android this is "movement not progress" and yet another example of fragmentation. I certainly like many aspects of Kotlin _but_ Java 14 is very nice AND enables greater participation from different roles (e.g. lower barrier to entry for the Spring Boot camp). I'd love to see Google uplifting the Java / JVM community and support modern Java syntax on Android.

As for Google building a better SDK, clearly the Android and Flutter teams do not see eye to eye...but maybe there will be lessons learned for both. I will be keeping an eye on Fuchsia with respect to developer tooling.

+1

And lastly to your point about lightweight desktop software, tiles don’t really have a place in the data process. They’re only really useful for the visualization aspect. And frankly, I think we’re reaching the capacity of the technique, we just might have some headroom in server efficiency.

Not totally sure what you mean on your last point...data can be feature centric (e.g. stored by feature id) or area centric (stored by area location) etc. Storing data by location is important far beyond visualisation and is abstracted in databases such as PostGIS/Postgres (a branded data structure). That said, I acknowledge that ArcGIS Pro, QGIS etc. have limited support for tiled data but of course that is changing. Safe funded much (all?) of the OGR MVT development afaik.

huge topic.

I wish I could learn to build my own tiles, vector or PNG. I don't really understand where the data comes from, how is data gathered and assembled.

There are many data providers out there. You might be interested in OpenMapTiles, which is a pipeline from OpenStreetMap (OSM) data. https://github.com/openmaptiles/openmaptiles

Also check out Maputnik http://maputnik.github.io/editor/

If you want to learn about "tiling schemes" then head over to https://www.maptiler.com/google-maps-coordinates-tile-bounds...

I'm also really curious about the choices involving the zoom level, how do you decide to render things depending on the zoom level, when is data discarded, to have good detail or better performance and lighter tiles. I would really be willing to try build lighter maps so I can have my own mapping software on a desktop machine.

Lots of different considerations - is a human going to look at the map? If so then a cartographer will determine what is going to be shown at a given scale. There are other constraints too, such as limited space to show data and also hidden constraints, such as the maximum amount of data for a region (e.g. ~500kb per tile in the case of mapbox vector tiles)

The data sizes and hardware requirements involved are generally pretty big. It could be interesting to see how much details one could achieve to make a "portable" map browser when limiting the data size to 2GB, 5GB or 10GB.

Lots of projects out there doing impressive things there. Quadtree tiles get you so far...k-d trees might yield other useful properties. Skobbler have some pretty impressive data compression technology (~12GiB for global coverage, routable and searchable...with some limitations - skobbler.com/apps). Of course the trick is to discard all that you don't need.

I would really like to ask why, on some mapping software, you can't see names of large enough cities/places/regions that are obviously there. It often makes it difficult to browse maps properly.

If there is limited budget then the effort to create appropriate labels is limited. Data sources can be limited / incomplete...there can be nuances between jurisdictions etc. and of course label prioritisation has been a longstanding problem. What happens when you rotate a map and the text labels collide with one another...which ones do you keep...which do you discard etc. These things are also context dependent...why not include continent names? Or region names? Or province names? What about the difference between physical and political geography? A cartographer can help ensure that the right information is available at the right time...whilst acknowledging that they have to tell little white lies in every map they make.

Cash: I donate to OSS projects at Xmas...and I do so with some news sources too. I give to projects that demonstrate good behaviours in the year - they are progressive, they are doing something I need and they have a plan on how to use the money. Some projects pass funds over to another project...if they do that then I don't donate to them and I consider the other project. I evaluate the above every Xmas...and sometimes I have to pull the plug esp. with news agencies that show signs of toxic behaviour. e.g. I stopped giving to the Guardian because their technology editors failed to write balanced articles, which then causes misinformation in the comments section requiring moderation etc. Openclipart.org also won't be receiving anything this year because they have done next to nothing at providing a solution to their "DDOS attack" and haven't been receptive to support.

Code: I make PRs, raise issues and open source my code where possible.

Thanks - I can see that. I am guessing that the smaller vocabulary is particularly useful in analogue systems. Perhaps W3W is viewed positively for (digital) cellular connections but might be inappropriate for other radio technology.

Agreed. I've had nothing but positive experiences with Revolut. Their app is excellent and I have been using it almost exclusively for the past 6 months. I have never had an issue contacting customer support (I do pay)...and it makes me smile how I can have crypto alongside fiat currency. I would say about 20% of my contact list also use Revolut and I have only heard positive experiences from them.

pretty sure folks will be able to just ask what it can do...and the response could of course look like a man page where folks can drill down further. I don't think we necessarily need to think the interactions will exclude a screen...but of course they could depending on the hardware / situation...today that activity might be driving...but perhaps we won't be driving all that much by the time this tech has advanced sufficiently.

sure - as part of the presentation, the UX guy also demo'ed something like botsociety.io. Essentially, he had a Facebook chat bot with buttons to hint what is possible (leading the conversation). That sort of interaction could be likened to messaging them versus talking to them...and perfectly suitable for an office or where you don't want to broadcast certain info.

So whilst ChatOps might be fairly basic today I am open to it becoming very much more advanced in the coming years.

as a mobile dev, I have been considering this with some UX folks. Few things going for AI/ML - conversation interfaces should be far cheaper/quicker to produce in comparison to traditional app development. Furthermore, talking and touch are natural ways to interact (e.g. pointing on a map whilst talking) vs endless long presses and menu items.

Whilst I have been involved in Android since the beginning I personally would not encourage younger folks to focus too much at the expense of new technologies (inc. blockchain tech for that matter).

That said, we hopefully have another 10 years!

Totally agree. There is massive confusion in the space...the tooling appears hard to maintain and often unloved. There is a whole push to get Android devs using Kotlin...I'd love to know the stats on actual usage. Personally, I see Kotlin as movement rather than progress.

At some point I think it would make sense to have a clean break. Personally, I'd love to see something like rust encouraged (possibly with JS frontend to ensure huge adoption). Probably never going to happen...so with that said, we'll probably end up with dart...suitable for writing macros around machine learning code.