Jump to content

sershe

Level 1
  • Posts

    8
  • Joined

  • Last visited

About sershe

Recent Profile Visitors

628 profile views

sershe's Achievements

1

Reputation

  1. Looking for a response from Evernote team, or a link to one, not people speculating unless they have something useful to add. TL;DR Legacy seems to stop working in a manner that indicates (1) issues on the server happening for many users on the same day, but (2) specific and "sticky" per client machine, with only some machines permanently breaking and others being fine with the same version/account/OS/network/... What can possibly cause such specific symptoms? I have some speculations below, can you please fix or just announce what's going on? Long details: I have 3 computers all running Windows 10, same network, ~same everything, and same 6.25 legacy (literally from the same installer on a usb stick). A few months ago, machine #1 legacy stopped syncing (password error, and connection error on logging out), I went here/to reddit and there were tons of people complaining about legacy breaking on the same day. However, machines #2-3 kept syncing fine. A few days back, machine #2 stopped syncing with the same symptoms. Again, bunch of people complain on the same day. And again, machine #3 is still syncing fine! And on the forums some people claim 6.25 works, I assume they are also lucky. Clearly this is not a local issue cause a bunch of users all break on the same day and there aren't many complaints on different days. At the same time, the broken-ness seems to be "sticky" per machine, surviving reinstall. I uninstalled on #2, nuked the DB and any registry settings left behind, reinstalled, and it won't even start - says immediately it's not online and cannot connect. Also machine #1 is also still broken, for months now. So, some machine ID (based on hardware/Windows install/IP/...) is probably involved? What can possibly cause such specific symptoms? As it happens, I work in distributed systems for a big tech co and I've been scratching my head. The only thing I can think of is that there's legacy-specific load-balancing somewhere based on machine ID, and as that legacy infrastructure is decommissioned in steps, the old machine IDs do not get re-assigned. So, they talk to dead instances while some "lucky" machines talk to the remaining live instances. If so, can you please fix this? Otherwise, it's really hard to come up with a charitable explanation here. If you are disabling legacy, disable legacy and announce it loud and clear. Are you trying to just create chaos and FUD among legacy users to have people upgrade?
  2. I can repro it on Windows and web. I guess we have different standards for immediately? You can clearly see for a split second when scrolling quickly, and note titles already being there, the empty size column that then gets populated. I checked web edition just now and it's still the case.
  3. I'd bet this idea is never going to be implemented. If you think about it - why would it need to be removed? It would typically be harder from the development perspective to treat the table fields differently - it would be easier in most circumstances to treat them all the same, i.e. sortable. The proximate reason Evernote 10 treats them differently is obvious if you open a large notebook, scroll back and forth to load all the notes, and the proceed to quickly scroll back and forth again. You'll see that, while (other than the usual Electron lag) note titles and dates are immediately available, there's an additional short gap when the note sizes for the notes being scrolled into view are blank. Evernote cannot sort by size because it doesn't have the sizes for all the notes in the UI control - they are loaded dynamically! Since to implement such a dynamic field system you'd need to make effort, it's clearly not accidental. I suspect the actual root cause simply has to do with limitations of Electron and/or their developers ("is Electron dumb, or are Electron developers?" "yes") - the more data the control has, the more laggy and slow it probably becomes. Since sorting by size is a rarely used feature, and the control is already slow compared to legacy, they are unlikely to add such a feature. To be clear, a competent developer could also implement a feature that sorts the notes outside of the control and then populates in within a few hours, at most. But, I bet this dynamic loading and other hacks (plus Electron itself) already make their codebase an ungodly mess (I've seen a few "clever" web app codebases in my time), and I don't expect there's a competent developer left there anyway. So, again, given how few users need it, it's unlikely to get implemented.
  4. I use Evernote legacy, and the first thing I'd do after it's finally killed is migrate and cancel my subscription of 13~ years. I noticed starting yesterday that the same version of legacy (6.25.1.9091) syncs on one machine, and doesn't sync on another. Everything is the same between machines, nothing was changed on either; the failure in Activity log is just an instant connection error that also gives me a public image url on Evernote site that supposedly cannot be downloaded - this url is accessible from the browser. Sadly I tried logging out/in and didn't save the url. Logging out and trying to log back in also fails with an instant connection error. Needless to say Evernote 10 connects easily on the same machine. And to reiterate, the same version of legacy can sync without issues on another machine on the same network. So, what is the official position on legacy, is it dead or not? <rant> And yes I've tried 10 just now - it's still laggy and forced updates are not acceptable, an average Electron developer is dumber than a bag of bricks so they'd break something every other update (and, as searching these forums clearly indicates, do break things with updates all the time). As for "10 is not that bad", I work as a high level software engineer at a major tech co, and do hiring sometimes. If I was presented with an Electron developer who thinks Electron (and the like) are a good idea, and my choices were "hire them in my team" and "spend the next month literally watching them starve to death for lack of income" I'd totally go with watching them starve to death. I understand modern users find laggy clunky apps acceptable cause they've barely used a good native app (like original Evernote!) in their lives, but I'm too old for this BS. </rant>
×
×
  • Create New...