Though ligatures when I first saw them looked really cool but trying them out I quickly realized how much I hated actually reading and writing code with them turned on. Cursive has also been an odd choice for monospace fonts to me, I don't like how they break the expected uniformity of the monospace text. Varying font weight, color and using italics has always been enough for me.
There is a great argument for having ultrasonic sensors and radar in a recent video by Rayan from FortNine discussing two fatal accidents involving tesla autopilot https://www.youtube.com/watch?v=yRdzIs4FJJg
I honestly cannot see the value in ReMarkable after the Kindle Scribe announcement. The kindle has a newer faster, 300dpi display vs 226dpi on the ReMarkable. I am waiting on reviews before ordering one for myself, but I can already see that Kindle Scribe is going to be disruptive for this segment.
I think ReMarkable's resolution is perfectly fine, and a higher DPI wouldn't make a significant difference.
However, it needs a better contrast. I can't tell if Scribe beats it on that, because in Scribe product videos their screen seems similarly dull, but other product shots have contrast so high it looks photoshopped.
Supposedly higher latency and worse experience when writing(also supposedly). I own Remarkable 2, and unless they can replicate same paper feeling, it won’t a replacement for Remarkable.
RM user base seems like a very niche Venn diagram:
1) People that love the feel of fountain pen writing.
2) People that love having all of their notes electronically.
I love what writing feels like, so I have a pen and paper and study offline (I typically throw out my notes). Generally, if you belong to just one of the two categories, you don't need to pay the RM premium.
The kindle will be using wacom emr which is more then adequate for most people. I never had a problem with the technology before and I don't think it will be practically worse. I can't imagine most people expect it to feel like writing on paper.
The reMarkable and the Kindle both use Wacom EMR, but that doesn't determine latency on these devices. It's all about the display's refresh rate... That's always been the Achilles Heel of ePaper. Honestly, the reMarkable 2 is perfectly fine for me.
I am hoping the carta 1200/1250 display which ever it ends up shipping with will help to reduce latency, but for my use case which is more reading and less note taking it is seemingly perfect.
I bought a Remarkable 2 - the UI design wasn’t there for me yet and I only persisted with it for a few days, but I am a big believer in the product category and would certainly give the next one a try. However, I think it will be forever niche. Not many people have any interest in writing by hand, and of those that do, only an few are so keen on digital organisation that they would buy one of these. It seems like a permanently small (but well heeled and discerning) target market, something for boutique tech companies to focus on, not giants. So I find it weird that Amazon is targeting this market at all - I don’t see how they plan to grow it into something big enough for them to care about. I feel like Kindle Scribe might just be an experiment that they will kill in a few years.
Anyone got any thoughts on this? Does Amazon have some big strategy that I’m missing here? How do they plan to persuade large numbers of people to buy into digital handwriting?
> Anyone got any thoughts on this? Does Amazon have some big strategy that I’m missing here? How do they plan to persuade large numbers of people to buy into digital handwriting?
Have you use office 365 or onenote? An iPad with the Apple pen recently? Any digital notes are organized by default, the latency and poor refresh rate makes eink impossible for replacing notebooks to me, but an LCD works great. Handwriting is already mainstream, as is using it on computer.
If you’re asking about Amazon most buyers of kindle fall between either upgrading every cycle and never using it, never upgrading their kindle keyboard, or more commonly never used it more than 3hr in total. Kindle sales are going to be good either way since type 1 buyers love tech for tech.
They've got a bigger screened Kindle, and included a pen with it.
They don't need to convince anyone to start taking notes on their Kindles, they just need to get people who want larger screens for reading to get them. Pen is a nice extra. And sure, there's 10% (pulled out of my behind, citation missing) of Scribe buyers who'd get it for note taking.
reMarkable is probably rightfully concerned since Amazon can easily outprice them, which they are already doing.
Same here: waiting for reviews before I jump on the wagon. Although, my primary motivation is to read PDF documents, especially the 2-column ones, than the prospect of taking notes or drawing. I hope it won't disappoint.
IMHO 10" is too small for PDFs. Now that Amazon is after their market, they should go someplace that Amazon isn't: devices with letter / A4 sized display.
I believe Sony and Fujitsu sell a 13.3" epaper device and of course the iPad is available in that size. There's a whole lot of space between the very limited $700 Quaderno and the super powerful $2000 iPad Pro.
It is not just about ocean plastic. Garbage is burned as fuel too in less developed countries. Stopping dumping of garbage in 2nd and 3rd world countries by developed/first world countries is going to benefit the environment in more ways than just reducing ocean plastics. We need to hold waste producers accountable. We need a systemic change, more push to reuse and recycle, better laws to limit production of single use plastics and a push towards repairability to limit production of e-waste.
>It is not just about ocean plastic. Garbage is burned as fuel too in less developed countries. Stopping dumping of garbage in 2nd and 3rd world countries by developed/first world countries is going to benefit the environment in more ways than just reducing ocean plastics.
But if only 2% of plastics worldwide is traded (source: same article I linked in my previous comment), and most of that is traded within the same region, how much waste could possibly end up getting shipped to less developed countries and burned? You'd still be better off trying to reduce domestic garbage production/burning in those countries.
> Garbage is burned as fuel too in less developed countries. Stopping dumping of garbage in 2nd and 3rd world countries by developed/first world countries is going to benefit the environment in more ways than just reducing ocean plastics.
what do you expect they'll burn for power if we stop paying them to take stuff to burn?
This was posted here 5 years ago [0], I had saved the file at the time and rediscovered it today while sorting through my collection of documents. The original link is now gone so I have linked to an archived version of it. While searching online not much can be found on it. I really appreciate the work Markus Bläser has put into this, and have no idea why the original file was taken down. There is little to no information on this online but I think it is really interesting and definitely worth a read.
This is so unethical and sadly not rare. I have had people reach out to me (twice, recently) on LinkedIn to interview for them (using names and credentials of people who have work authorization for USA) and the offer is usually a fixed rate + commission per job per month for the lifetime of the job. They hire skilled engineers to secure the jobs for them while outsourcing the actual work. So the scam can go further than just outsourcing the work to people with potentially far lower skills.
Saving bandwidth is really not the actual super power. The main advantage is being able to save network requests by fetching all required data in the same request.
> The main advantage is being able to save network requests by fetching all required data in the same request.
This is not really GraphQL's selling point.
GraphQL's only selling point is this handwaving-driven promise that dev teams no longer need backend work to get an API that returns the data they want.
The promise is that frontend teams simply put together a query and the server magically returns what they want.
Of course the people promising this magic just so happen to be the same people trying to sell you backend services.
I know I can make an API endpoint in Rails equally as fast as writing a query in GraphQL and the code needed to use it. I don't really buy into GraphQL yet since I have not come across a strong enough advantage of using it in my carrier. Although I do see the advantage of basically being able to run SQL through the browser. Unfortunately it is just one of may technologies over hyped by JavaScript developers.
Agreed - REST APIs can include a field mask or similar for sparse selection on a single entity but you'll still need several requests to fetch fields on related entities.
I would love to see what this will bring to K9 mail. I hope having the support of Thunderbird will allow K9 to really get some much needed polish. My preferred app right now is FairMail, its interface takes some getting used to and settings layout is very confusing but once I did manage to get it setup, it became clear that I preferred its extensive customizability and sidebar vs K9 when it comes to managing emails across multiple accounts. They are basically the only two FLOSS Email apps worth using on android, so K9 getting some extra support is really awesome.
One measure is the number of stars on github and active contributors 49.7k vs 25.7k and 737 vs 79. The other measure can be the number of new extensions being written for each of them (particularly extremely high quality ones like telescope). Searching `nvim` on github yields many plugins which are advertising the Neovim editor by having it in their name, some of these are even ones which support vim e.g. Shougo/denite.nvim all of which point to the fact that neovim is a huge success and is on tract to overtake vim. It would not be an exaggeration to say that a lot if this is due to first class lua support in Neovim. By adding nice features like treesitter and LSP it has become an improved version of vim, an editor that actually understands the code being edited beyond simple text objects (e.g. https://youtu.be/E4uaPs9e9UU?t=68)
