I was able to get FireTray (assuming you want an unread count in your system tray) working by changing the supported version flag in the.xpi file (which is just a ZIP file).
Will LookOut survive the WebExtensions shift? Only time will tell... though I feel it has a better chance of pulling through than the EWS plugin I use for dealing with Exchange calendars...
Anecdotal: Outlook crashes/hangs/just stops communicating with the internet on a somewhat regular basis, though I can't say it's a daily occurrence where I work. In a company of 30-50, it seems I need to fiddle with something on someone's computer once every few days. Also very aggressive about trying to use IPv6, even on a network that does not have it enabled, and takes ages to launch with large (multi-GB) PST files (though it is not as bad as it was many years ago). We had one fellow whose instance would reliably crash the first time it was launched, every single day, even after uninstall/purge/reinstall; no cause for that was ever found. Several of my coworkers, as well as myself, run Thunderbird, and nobody has reported any issues whatsoever. Regarding gmail (as a web service), it's very nice to be able to access all of your e-mail while completely disconnected from the Internet... webmail is nice, but completely useless when your Internet sucks. Gmail does support IMAP/SMTP, which I use at home (though via SeaMonkey, mostly for the heck of it).
Also, you may have read too deeply into one of my statements: I was not attempting to insinuate that the power users (who i define here from a perspective of need more than capability) I loosely describe are the only people who actively recommend/support the use of their products. OSS seems, to me, to work best when propagated via word-of-mouth. They simply don't have the money to burn on marketing campaigns that appeal to the more fickle among us, so finding ways to leverage your existing userbase is something to strongly consider. However, I will suggest these power users have disproportionate sway compared to the average user, so probably best to appease (or at least not completely drive them off) them where it is reasonable to do so.
Regarding help, what are we to even do, especially those of us without the requisite skills to engage such a large project? How much resistance to their overall vision for the product will they allow? If WebExtensions are their way forward, at least for the front-end of the software, what options remain for the back-end service interaction protocols? If they've actually thought this through, which I hold no shortage of hope for, perhaps it is not as bad as I make it out to be.
This is sadly (at least partially) true, and I really wish it wasn't the case. It also doesn't help that large projects are not very agile, but I'll accept that the current codebase probably has them, a bit cornered... how many original developers are still with the project? Regarding extensions/plugins, some sort of middle ground needs to be had: XUL was perhaps too flexible, but WebExtensions is quite a big step down in terms of extensibility (and I dread the thought of bringing it to a mail client as the sole means of extensibility).
Also not suggesting that the EWS plugin I references is somehow the end of the world to lose easy use of, but don't fall victim to the mentality of 'oh, it's just.1%(or smaller) of our userbase' when that tiny percentage represents thousands (or when you're, e.g. Microsoft, millions) of people. As with (i suspect, i haven't counted) many people, even approaching a large OSS project is intimidating due to the tendency for such projects to categorically ignore stuff coming from outsiders.
I do, however, respect the notion of avoiding a 'too many cooks in the kitchen' or 'too many chiefs' type of situation; we can't all have what we want, but we're talking about gutting functionality that has been available for... a long time, so I'm going to maintain my stance that trying to do this to one of the last high-featured, semi-actively developed, non-proprietary mail clients is a bit of a boneheaded move. We're not talking about something like DDE, which MS is only recently getting around to (partially) killing off, but more like if Microsoft decided to dump GDI+ and/or Win32 API and forced WPF/.Net upon us all in some future Win10 update. Bad analogy is bad, but I feel that it is at least a somewhat decent representation of such a grand change at a different scale.
This makes the assumption that this market had 10000 points to drop... or can those indices go negative? (actual question, I'm not overly knowledgeable on this topic)
... to a possibly surprising recipient: Despite being a crusty/unreliable piece of crap, Outlook has no shortage of features, and exposes them in not-particularly-difficult-to-find ways. The UI is probably the least 'afflicted' by the ribbon of the various Office products I've used in recent history, as the ribbon winds up getting used more like a conventional menu. While we are not expecting Thunderbird to be a full-featured Outlook knock-off, the current set of features (while missing a few) is still quite good; any reduction thereof means they're taking a step back, and no longer see themselves as a viable competitor to the old behemoth (regardless of if it is true or not.
Closing statements, directed towards The Mozilla Foundation:
I will continue to use Thunderbird, even older versions, until it becomes a security liability and/or no longer does what I need it to do.
I will have little choice but to return to Outlook for work purposes, if WebExtensions is to be ramrodded down our collective gullets.
Thunderbird may very well be your last opportunity to prove to the world that you have not completely lost your way; don't blow it.
As well it should. It's like there's this ongoing competition to see who can crank out the flattest UI, with the least visible boundaries between text (excluding whitespace) and the fewest meaningful features exposed through it.
Well, are they going to roll EWS support into their main codebase (currently functional through a plugin)? It's almost like they strongly desire these products to die. They seem to have forgetten that the market they need to be directly pandering to isn't necessarily their bulk consumer base... it's the people that recommend/support (tense is probably wrong at this point) the use of their products.
I've seen 18/2 or 18/4 used in similar situations, occasionally with pairs of wires shorted together. Quality is somewhat lower, usually, compared to Romex; I couldn't recommend using it for anything close to the normal current limit for the wire. You also have skin effect to be concerned with in solid wire, though not likely to be a huge issue at audio frequency and reasonable power.
Was also reading Yamaha's site on XP amps and noticed they described their lineup with "5 Models from 700W to 100W"... why the descending order?
Kind of a special case, and not 100% relevant, but if you get a static IP through Comcast, you're required to rent their shit routers. Take your pick, a Cisco with the defective Puma 6 chipset and corresponding wonky performance, or an SMC with horribly broken IPv6 support (it does, however, work with a single IPv6 client...). I suggest this is a small sliver of one possible future that lies before us.
As a temporary solution, I wonder if the old FEMA trailers have finished outgassing all their formaldehyde... perhaps someone has a collection of those going.
Slashdot Mirror
I made mention of this because this story came out yesterday: https://tech.slashdot.org/stor...
For clarity, one must edit install.rdf and change the 38.0 to some much higher number.
I was able to get FireTray (assuming you want an unread count in your system tray) working by changing the supported version flag in the .xpi file (which is just a ZIP file).
Will LookOut survive the WebExtensions shift? Only time will tell... though I feel it has a better chance of pulling through than the EWS plugin I use for dealing with Exchange calendars...
Anecdotal: Outlook crashes/hangs/just stops communicating with the internet on a somewhat regular basis, though I can't say it's a daily occurrence where I work. In a company of 30-50, it seems I need to fiddle with something on someone's computer once every few days. Also very aggressive about trying to use IPv6, even on a network that does not have it enabled, and takes ages to launch with large (multi-GB) PST files (though it is not as bad as it was many years ago). We had one fellow whose instance would reliably crash the first time it was launched, every single day, even after uninstall/purge/reinstall; no cause for that was ever found. Several of my coworkers, as well as myself, run Thunderbird, and nobody has reported any issues whatsoever. Regarding gmail (as a web service), it's very nice to be able to access all of your e-mail while completely disconnected from the Internet... webmail is nice, but completely useless when your Internet sucks. Gmail does support IMAP/SMTP, which I use at home (though via SeaMonkey, mostly for the heck of it).
Also, you may have read too deeply into one of my statements: I was not attempting to insinuate that the power users (who i define here from a perspective of need more than capability) I loosely describe are the only people who actively recommend/support the use of their products. OSS seems, to me, to work best when propagated via word-of-mouth. They simply don't have the money to burn on marketing campaigns that appeal to the more fickle among us, so finding ways to leverage your existing userbase is something to strongly consider. However, I will suggest these power users have disproportionate sway compared to the average user, so probably best to appease (or at least not completely drive them off) them where it is reasonable to do so.
Regarding help, what are we to even do, especially those of us without the requisite skills to engage such a large project? How much resistance to their overall vision for the product will they allow? If WebExtensions are their way forward, at least for the front-end of the software, what options remain for the back-end service interaction protocols? If they've actually thought this through, which I hold no shortage of hope for, perhaps it is not as bad as I make it out to be.
This is sadly (at least partially) true, and I really wish it wasn't the case. It also doesn't help that large projects are not very agile, but I'll accept that the current codebase probably has them, a bit cornered... how many original developers are still with the project? Regarding extensions/plugins, some sort of middle ground needs to be had: XUL was perhaps too flexible, but WebExtensions is quite a big step down in terms of extensibility (and I dread the thought of bringing it to a mail client as the sole means of extensibility).
.1%(or smaller) of our userbase' when that tiny percentage represents thousands (or when you're, e.g. Microsoft, millions) of people. As with (i suspect, i haven't counted) many people, even approaching a large OSS project is intimidating due to the tendency for such projects to categorically ignore stuff coming from outsiders.
Also not suggesting that the EWS plugin I references is somehow the end of the world to lose easy use of, but don't fall victim to the mentality of 'oh, it's just
I do, however, respect the notion of avoiding a 'too many cooks in the kitchen' or 'too many chiefs' type of situation; we can't all have what we want, but we're talking about gutting functionality that has been available for... a long time, so I'm going to maintain my stance that trying to do this to one of the last high-featured, semi-actively developed, non-proprietary mail clients is a bit of a boneheaded move. We're not talking about something like DDE, which MS is only recently getting around to (partially) killing off, but more like if Microsoft decided to dump GDI+ and/or Win32 API and forced WPF/.Net upon us all in some future Win10 update. Bad analogy is bad, but I feel that it is at least a somewhat decent representation of such a grand change at a different scale.
In retrospect, it probably sounds like I'm straight out of 1995, or just plain can't do math.
This makes the assumption that this market had 10000 points to drop... or can those indices go negative? (actual question, I'm not overly knowledgeable on this topic)
Also, in this context, the concept of fixing 'technical debt' reads to me like 'defaulting on a loan'.
... to a possibly surprising recipient: Despite being a crusty/unreliable piece of crap, Outlook has no shortage of features, and exposes them in not-particularly-difficult-to-find ways. The UI is probably the least 'afflicted' by the ribbon of the various Office products I've used in recent history, as the ribbon winds up getting used more like a conventional menu. While we are not expecting Thunderbird to be a full-featured Outlook knock-off, the current set of features (while missing a few) is still quite good; any reduction thereof means they're taking a step back, and no longer see themselves as a viable competitor to the old behemoth (regardless of if it is true or not.
Closing statements, directed towards The Mozilla Foundation:
I will continue to use Thunderbird, even older versions, until it becomes a security liability and/or no longer does what I need it to do.
I will have little choice but to return to Outlook for work purposes, if WebExtensions is to be ramrodded down our collective gullets.
Thunderbird may very well be your last opportunity to prove to the world that you have not completely lost your way; don't blow it.
As well it should. It's like there's this ongoing competition to see who can crank out the flattest UI, with the least visible boundaries between text (excluding whitespace) and the fewest meaningful features exposed through it.
Well, are they going to roll EWS support into their main codebase (currently functional through a plugin)? It's almost like they strongly desire these products to die. They seem to have forgetten that the market they need to be directly pandering to isn't necessarily their bulk consumer base... it's the people that recommend/support (tense is probably wrong at this point) the use of their products.
Was immediately reminded of this el reg article:
https://www.theregister.co.uk/...
Trying that transfer in MS-DOS:
C:\Users\bob>move trust elsewhere
The system cannot find the file specified.
Hmm, might be a platform issue...
bob@notreallyacomputer ~ % mv trust elsewhere
mv: cannot stat 'trust': No such file or directory
Nope, can't transfer what's not there...
It's a concise way of describing a short nap taken with a specific goal.
As I recall, you could identify if someone was online by the ability to view their 'profile', regardless of their apparent status.
We... knew him.
Also, this is why I should never be the one to write the eulogy.
I've seen 18/2 or 18/4 used in similar situations, occasionally with pairs of wires shorted together. Quality is somewhat lower, usually, compared to Romex; I couldn't recommend using it for anything close to the normal current limit for the wire. You also have skin effect to be concerned with in solid wire, though not likely to be a huge issue at audio frequency and reasonable power.
... why the descending order?
Was also reading Yamaha's site on XP amps and noticed they described their lineup with "5 Models from 700W to 100W"
http://dilbert.com/strip/1995-... good times.
Kind of a special case, and not 100% relevant, but if you get a static IP through Comcast, you're required to rent their shit routers. Take your pick, a Cisco with the defective Puma 6 chipset and corresponding wonky performance, or an SMC with horribly broken IPv6 support (it does, however, work with a single IPv6 client...). I suggest this is a small sliver of one possible future that lies before us.
Integrate a living creature, e.g. a rat, or even an insect, and it is then technically a cyborg. Cyborgs are not robots.
My experience was that it was slow to load its menus, but aside from that, it seemed to do what it's supposed to.
Indeed... I definitely need a little bit of structure to my life... but not that much structure!
As a temporary solution, I wonder if the old FEMA trailers have finished outgassing all their formaldehyde... perhaps someone has a collection of those going.