osmscout-server VS micro-editor

Pure Maps with OSM Scout Server for offline mapping and geolocation

- build a minimal web page showing a Leaflet or a MapLibre widget, connected to a backend built using a compiled language like C++ or D, itself connecting to OSM Scout Server to provide the tiles. Or to OSM Scout Server directly if it is possible.

The last option is probably the most lightweight solution, provided you probably have a browser already running on your phone. I'm not saying this out of my ass by the way, I'm building an SMS app using Svelte for the user interface and D for the backend connecting to the modem and managing the SQLite database. It's way faster than chatty.

[1] https://openrepos.net/content/rinigus/pure-maps

[2] https://rinigus.github.io/osmscout-server/

There are on device or even in browser renderers that only need remote or locally stored vector data to render the map. This moves the burde of rendering to user devices that should be more than capable for this today (especially if you use a GPU renderer) and makes you server into just a dumb data pipe that should be able to scale much better & more cheaply.

One such renderer available via Qt/QML:

https://doc.qt.io/qt-5/location-plugin-mapboxgl.html

Alternatively you can have a local daemon running that does the tile rendering on your device from offline data packs. This way even "legacy" apps requiring simple bitmap tiles will work without (major) changes. One such project providing this (among other APIs) is OSM Scout Server:

https://github.com/rinigus/osmscout-server

To see more screenshots of micro, showcasing some of the default color schemes, see here.

Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:

- gdu: a NCDU clone, much faster on SSD mounts [1]

- duf: a `df` clone with a nicer interface [2]

- massren: a `vidir` clone (simpler to use but with fewer options) [3]

- gotop: a `top` clone [4]

- micro: a nice TUI editor [5]

Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.

[1]: https://github.com/dundee/gdu

[2]: https://github.com/muesli/duf

[3]: https://github.com/laurent22/massren

[4]: https://github.com/xxxserxxx/gotop

[5]: https://github.com/zyedidia/micro

> The worst way to store and manipulate text is to use an array.

Claim made from theoretical considerations, without any actual reference to real-world editors. The popular Micro[1] text editor uses a simple line array[2], and performs fantastically well on real-world editing tasks.

Meanwhile, ropes are so complicated that even high-quality implementations have extremely subtle bugs[3] that can lead to state or content corruption.

Which data structure is "best" is not just a function of its asymptotic performance. Practical considerations are equally important (arguably more so).

[1] https://github.com/zyedidia/micro

[2] https://github.com/zyedidia/micro/blob/master/internal/buffe...

[3] https://github.com/cessen/ropey/pull/67

There are two main ways to configure sudo.The first one is using the sudoers file.It is located at /etc/sudoers for Linux,and /usr/local/etc/sudoers for FreeBSD respectively.The paths are different,but the configuration works in the same way. A typical sudoers file looks like this. The sudoers file must be edited with the visudo command,which ensures the config is free of errors.Running this command as the root user will result in opening vi by default.If you want to use a different editor you can set the VISUAL environment varaible to the editor you want. For example,if you want to use micro as the text editor run:

found that micro has dedicated info page for copy paste

micro: winget install zyedidia.micro